From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Gabriel C <nix.or.die@googlemail.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Arjan van de Ven <arjan@infradead.org>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Avi Kivity <avi@qumranet.com>
Subject: Re: [git pull] x86 PAT changes
Date: Sat, 26 Apr 2008 09:43:18 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0804260940290.2813@woody.linux-foundation.org> (raw)
In-Reply-To: <20080426154123.GA7295@elte.hu>
On Sat, 26 Apr 2008, Ingo Molnar wrote:
> * Gabriel C <nix.or.die@googlemail.com> wrote:
> >
> > It seems like the update triggers some compiler bug.
> >
> > Setting CC_OPTIMIZE_FOR_SIZE=n fixed that btw.
> >
> > I don't have the time right now but later on today I will compile
> > gcc43_svn_branch and test again with CC_OPTIMIZE_FOR_SIZE=y and see
> > what I get.
> >
> > Ingo sorry for the noise.
>
> no problem and it's not noise even if it turns out to be a compiler
> problem - we very much want to know about them when they affect the
> kernel.
Indeed. Often these kinds of compiler issues are also actually our bugs,
where some code generation thing just happened to hide the fact that we
did something wrong.
So Gabriel, it would be wondeful if you could try to pinpoint where the
problem happens. That said, especially if you are using something like a
self-compiled gcc from the current SVN tree, that obviously does make it a
*lot* more likely that you are hitting a real compiler bug.
(But even then, if you can pinpoint it, I bet the gcc people would be
really happy to hear about it.)
Linus
prev parent reply other threads:[~2008-04-26 16:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 22:56 Ingo Molnar
2008-04-25 23:43 ` Linus Torvalds
2008-04-26 0:06 ` H. Peter Anvin
2008-04-26 1:12 ` Linus Torvalds
2008-04-26 8:56 ` Ingo Molnar
2008-04-26 16:54 ` Pallipadi, Venkatesh
2008-04-26 17:15 ` Linus Torvalds
2008-04-26 18:32 ` Venki Pallipadi
2008-04-26 19:07 ` [patch] x86, PAT: disable /dev/mem mmap RAM with PAT Ingo Molnar
2008-04-26 9:57 ` [git pull] x86 PAT changes Ingo Molnar
2008-04-26 13:40 ` Gabriel C
2008-04-26 14:42 ` Ingo Molnar
2008-04-26 15:37 ` Gabriel C
2008-04-26 15:41 ` Ingo Molnar
2008-04-26 16:43 ` Linus Torvalds [this message]
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=alpine.LFD.1.10.0804260940290.2813@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=avi@qumranet.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nix.or.die@googlemail.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
/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
all inboxes | Powered by JetHome®