Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: James Hogan <james.hogan@mips.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, <linux-mips@linux-mips.org>,
	"Waldemar Brodkorb" <wbx@openadk.org>,
	Florian Fainelli <florian@openwrt.org>
Subject: Re: undefined reference to `__multi3' when building with gcc 7.x
Date: Wed, 6 Dec 2017 08:50:34 +0100	[thread overview]
Message-ID: <20171206085034.3869dc9d@windsurf.lan> (raw)
In-Reply-To: <20171205234923.GK27409@jhogan-linux.mipstec.com>

Hello,

On Tue, 5 Dec 2017 23:49:24 +0000, James Hogan wrote:

> > I'm still facing this problem. There was a lengthy thread about it back
> > in August when I reported the problem, but then it calmed down, with no
> > real solution proposed.
> > 
> > Are there plans to fix this at some point?  
> 
> I recently fixed a similar issue in 64r6[el]_defconfig, but its not the
> same as it applies to all gcc versions on mips64r6. Given Ralf appears
> to be busy I'll take a look.

Thanks a lot. If you need some help to reproduce the problem, let me
know, I can provide simple instructions to produce it.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: James Hogan <james.hogan@mips.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	linux-mips@linux-mips.org, Waldemar Brodkorb <wbx@openadk.org>,
	Florian Fainelli <florian@openwrt.org>
Subject: Re: undefined reference to `__multi3' when building with gcc 7.x
Date: Wed, 6 Dec 2017 08:50:34 +0100	[thread overview]
Message-ID: <20171206085034.3869dc9d@windsurf.lan> (raw)
Message-ID: <20171206075034.h4FlF8jnw15WgdYIq4yckym-leQh8IXoUoML8HMLNng@z> (raw)
In-Reply-To: <20171205234923.GK27409@jhogan-linux.mipstec.com>

Hello,

On Tue, 5 Dec 2017 23:49:24 +0000, James Hogan wrote:

> > I'm still facing this problem. There was a lengthy thread about it back
> > in August when I reported the problem, but then it calmed down, with no
> > real solution proposed.
> > 
> > Are there plans to fix this at some point?  
> 
> I recently fixed a similar issue in 64r6[el]_defconfig, but its not the
> same as it applies to all gcc versions on mips64r6. Given Ralf appears
> to be busy I'll take a look.

Thanks a lot. If you need some help to reproduce the problem, let me
know, I can provide simple instructions to produce it.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2017-12-06  7:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 20:55 undefined reference to `__multi3' when building with gcc 7.x Thomas Petazzoni
2017-08-04  0:05 ` Ralf Baechle
2017-08-04 15:19   ` Ralf Baechle
2017-08-04 15:41     ` Thomas Petazzoni
2017-08-04 22:25       ` Ralf Baechle
2017-08-05 11:56         ` Thomas Petazzoni
2017-08-07  8:34           ` Ralf Baechle
2017-08-13 20:46             ` Thomas Petazzoni
2017-08-17  7:15               ` Ralf Baechle
2017-08-17  8:49                 ` Matthew Fortune
2017-08-17 22:19                   ` Ralf Baechle
2017-10-07 19:22                     ` Thomas Petazzoni
2017-11-07 17:39                     ` Thomas Petazzoni
2017-08-17  1:01         ` Maciej W. Rozycki
2017-08-17  1:01           ` Maciej W. Rozycki
2017-12-03  9:56 ` Thomas Petazzoni
2017-12-05 23:49   ` James Hogan
2017-12-05 23:49     ` James Hogan
2017-12-06  7:50     ` Thomas Petazzoni [this message]
2017-12-06  7:50       ` Thomas Petazzoni
2017-12-07  7:20       ` [PATCH] MIPS: Implement __multi3 for GCC7 MIPS64r6 builds James Hogan
2017-12-08 23:52         ` Maciej W. Rozycki
2017-12-08 23:52           ` Maciej W. Rozycki
2017-12-09  7:15           ` James Hogan
2017-12-09  7:15             ` James Hogan
2017-12-27  8:31         ` Waldemar Brodkorb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171206085034.3869dc9d@windsurf.lan \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=florian@openwrt.org \
    --cc=james.hogan@mips.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=wbx@openadk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox