From: Adrian Bunk <bunk@kernel.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Dave Airlie <airlied@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-ext4@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: kerneloops.org: 2.6.26-rc possible regression in ext3
Date: Thu, 19 Jun 2008 18:43:35 +0300 [thread overview]
Message-ID: <20080619154335.GC2721@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <485A7AF4.4080307@linux.intel.com>
On Thu, Jun 19, 2008 at 08:27:48AM -0700, Arjan van de Ven wrote:
> Adrian Bunk wrote:
>> On Thu, Jun 19, 2008 at 08:18:39AM -0700, Arjan van de Ven wrote:
>>> Adrian Bunk wrote:
>>>> On Thu, Jun 19, 2008 at 06:40:05AM -0700, Arjan van de Ven wrote:
>>>>> Adrian Bunk wrote:
>>>>>> Expect a lot more of this to pop up in the future.
>>>>>> Should we #error for gcc 4.3.1?
>>>>> it/s better to find if the gcc guys made a testcase for this bug (they normally do) and
>>>>> test based on that.
>>>> The gcc Bugzilla contains a testcase.
>>>>
>>>> But how do you plan to integrate it into a kernel build?
>>> we already have several of these.
>>> Just look at scripts/gcc-x86_64-has-stack-protector.sh for an example of such a beast.
>>
>> Checking whether gcc supports some flags is easy.
>
> have you actually looked at this script?
> You didn't, since the script doesn't check if gcc supports some flag.
> It checks very specifically for a code generation pattern...
>
> Please go look at the script first before responding.
I did look, but I missed the last pipe...
Do we know for sure this bug can only trigger on 32bit x86?
Or is there anything else I miss in gcc-x86_64-has-stack-protector.sh
that allows to use this approach to check for wrong code generation
caused by platform independent gcc bugs?
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-06-19 15:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 5:36 kerneloops.org: 2.6.26-rc possible regression in ext3 Arjan van de Ven
2008-06-19 5:42 ` Dave Airlie
2008-06-19 5:48 ` Arjan van de Ven
2008-06-19 6:42 ` Linus Torvalds
2008-06-19 7:09 ` Arjan van de Ven
2008-06-19 8:11 ` Adrian Bunk
2008-06-19 8:32 ` Mikael Pettersson
2008-06-19 10:49 ` Adrian Bunk
2008-06-19 13:40 ` Arjan van de Ven
2008-06-19 15:10 ` Adrian Bunk
2008-06-19 15:18 ` Arjan van de Ven
2008-06-19 15:25 ` Adrian Bunk
2008-06-19 15:27 ` Arjan van de Ven
2008-06-19 15:43 ` Adrian Bunk [this message]
2008-06-19 14:00 ` Eric Sandeen
2008-06-19 14:07 ` Arjan van de Ven
2008-06-19 14:17 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2008-06-19 5:34 Arjan van de Ven
2008-06-19 6:01 ` Linus Torvalds
2008-06-19 6:09 ` Arjan van de Ven
2008-06-19 6:14 ` Linus Torvalds
2008-06-19 6:40 ` Linus Torvalds
2008-06-20 15:34 ` Bill Nottingham
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=20080619154335.GC2721@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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