public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Andreas Schwab <schwab@suse.de>, Martin Sebor <msebor@redhat.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] target/65286 - Disable multilib for ppc64le
Date: Wed, 04 Mar 2015 16:19:00 -0000	[thread overview]
Message-ID: <54F73089.8040308@redhat.com> (raw)
In-Reply-To: <mvmzj7sswrv.fsf@hawking.suse.de>

On 03/04/15 06:43, Andreas Schwab wrote:
> Martin Sebor <msebor@redhat.com> writes:
>
>> The attached patch resolves PR 65286 by adding --disable-multilib
>> when configuring for a ppc64le target.
>
> If powerpc64le doesn't want multilib it should not set any multilib
> parameters.
Agreed, and it's debatable whether or not ppc64le should have any 
multilibs at this time.  That's a decision I leave to the ppc 
maintainers to answer.

I think the concern is that simply disabling the multilib without 
looking at the underlying failure may be papering over a real bug.

jeff

  reply	other threads:[~2015-03-04 16:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04  0:59 Martin Sebor
2015-03-04 13:20 ` Segher Boessenkool
2015-03-04 13:43 ` Andreas Schwab
2015-03-04 16:19   ` Jeff Law [this message]
2015-03-04 16:40     ` Martin Sebor
2015-03-04 16:47       ` Jeff Law
2015-03-04 17:17       ` Andreas Schwab
2015-03-04 20:22         ` Martin Sebor
2015-03-05  4:06           ` Alan Modra
2015-03-05 23:14             ` Alan Modra
2015-03-09 18:00               ` David Edelsohn
2015-03-10  6:13                 ` Markus Trippelsdorf
2015-03-10  7:28                   ` Alan Modra
2015-03-10  7:33                     ` Markus Trippelsdorf
2015-03-10  7:56                       ` Jakub Jelinek
2015-03-10 11:08                         ` Markus Trippelsdorf
2015-03-10 12:06                           ` Alan Modra
2015-03-10 12:10                             ` Jakub Jelinek
2015-03-10 13:27                               ` David Edelsohn

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=54F73089.8040308@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=msebor@redhat.com \
    --cc=schwab@suse.de \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).