public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Andrew Pinski" <pinskia@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: Fix i686-linux --enable-targets=all
Date: Mon, 06 Aug 2007 13:39:00 -0000	[thread overview]
Message-ID: <de8d50360708060639n563fa63qd2c0e0d3dc7a2a9f@mail.gmail.com> (raw)
In-Reply-To: <20070806133655.GA30770@caradoc.them.org>

On 8/6/07, Daniel Jacobowitz <drow@false.org> wrote:
> Right now all tests fail if you build an i686-linux compiler with
> --enable-targets=all and test the -m64 multilib, while using bleeding
> edge binutils.  This was already fixed for x86_64, but different
> arrangement of t-* fragments means that the fix didn't cover
> i686-linux.
>
> Is this OK?  I have not been able to get my build server to bootstrap
> an --enable-targets=all compiler due to the different way Debian /
> Ubuntu handle multiple architecture support, but I did build 64-bit
> libgcc and verify that crtend.o no longer has a zero terminator
> followed by some unwind information.

I think this is PR 32840.

Thanks,
Andrew Pinski

  reply	other threads:[~2007-08-06 13:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06 13:37 Daniel Jacobowitz
2007-08-06 13:39 ` Andrew Pinski [this message]
2007-08-06 13:41 ` H.J. Lu
2007-08-06 13:51   ` Daniel Jacobowitz
2007-08-06 14:13     ` H.J. Lu
2007-08-06 14:24       ` Daniel Jacobowitz
2007-08-06 14:56         ` H.J. Lu
2007-08-06 15:07           ` Daniel Jacobowitz
2007-08-06 16:05         ` Paolo Bonzini
2007-08-06 16:11           ` Daniel Jacobowitz
2007-08-06 16:29           ` H.J. Lu
2007-08-06 18:34 Paolo Bonzini
2007-08-06 19:53 ` H.J. Lu

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=de8d50360708060639n563fa63qd2c0e0d3dc7a2a9f@mail.gmail.com \
    --to=pinskia@gmail.com \
    --cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).