From: Andi Kleen <andi@firstfloor.org>
To: "Török Edwin" <edwintorok@gmail.com>
Cc: "Thomas Gleixner mingo@redhat.com" <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: gcc-4.3 considers unaligned accesses on X86 as undefined
Date: 26 Mar 2008 06:30:17 +0100 [thread overview]
Message-ID: <87d4pinjbq.fsf@basil.nowhere.org> (raw)
In-Reply-To: <47E965BD.7010604@gmail.com>
Török Edwin <edwintorok@gmail.com> writes:
> At -O3 it generates vectorized code that _relies_ on the fact that
> pointers are always aligned (unless you use packed attributes, etc.),
> and the resulting code crashes if the pointer is unaligned. (-O3 -msse
> on 32-bit, and simply -O3 on 64-bit since -msse is default)
The 2.6 kernel disables SSE and MMX code generation explicitely.
2.4 should be also safe unless someone misguided recompiles it with -O3.
-Andi
prev parent reply other threads:[~2008-03-26 5:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 20:51 gcc-4.3 considers unaligned accesses on X86 as undefined Török Edwin
2008-03-25 20:56 ` H. Peter Anvin
2008-03-25 21:11 ` Alan Cox
2008-03-26 5:30 ` Andi Kleen [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=87d4pinjbq.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=edwintorok@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.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