From: Andrew Walrond <andrew@walrond.org>
To: sparclinux@vger.kernel.org
Subject: Re: GCC 4.2.1 produces broken 2.6.22.1 kernel.
Date: Wed, 17 Oct 2007 12:14:32 +0000 [thread overview]
Message-ID: <4715FCA8.4090507@walrond.org> (raw)
In-Reply-To: <46B7600A.3060700@walrond.org>
David Miller wrote:
>
> The dataflow pass doesn't mark global registers correctly, and
> the new thing in gcc-4.2.x vs. gcc-4.1.x is that it uses the
> dataflow pass for the loop optimizers.
>
I look forward to testing this when you think it's ready. As well as the
kernel, I discovered several other packages which behave oddly and/or
crash when compiled 64bit with 4.2, but seem just fine with 4.1. (My
custom server distro is pure 64bit for simplicity sake (only 1 version
of libs etc etc), so I'm probably the only one to have noticed).
Andrew Walrond
next prev parent reply other threads:[~2007-10-17 12:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 17:53 GCC 4.2.1 produces broken 2.6.22.1 kernel Andrew Walrond
2007-08-08 5:44 ` David Miller
2007-08-25 5:18 ` David Miller
2007-08-25 8:05 ` Andrew Walrond
2007-08-25 9:51 ` David Miller
2007-10-17 11:38 ` David Miller
2007-10-17 12:14 ` Andrew Walrond [this message]
2007-10-18 1:09 ` David Miller
2007-10-18 9:52 ` Andrew Walrond
2007-10-18 10:27 ` David Miller
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=4715FCA8.4090507@walrond.org \
--to=andrew@walrond.org \
--cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.