From: Jakub Jelinek <jakub@redhat.com>
To: antirez <antirez@invece.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: epic100.c, gcc-2.95.2 compiler bug!
Date: Fri, 7 Sep 2001 10:26:02 -0400 [thread overview]
Message-ID: <20010907102602.J25384@devserv.devel.redhat.com> (raw)
In-Reply-To: <20010903130404.B1064@lxmayr6.informatik.tu-muenchen.de> <20010907160159.C621@lxmayr6.informatik.tu-muenchen.de> <20010907160315.D621@lxmayr6.informatik.tu-muenchen.de> <20010907161323.B31574@blu>
In-Reply-To: <20010907161323.B31574@blu>; from antirez@invece.org on Fri, Sep 07, 2001 at 04:13:23PM +0200
On Fri, Sep 07, 2001 at 04:13:23PM +0200, antirez wrote:
> The following seems a gcc 3.0 bug, not sure it was fixed in gcc 3.01.
>
> See the assembly generated with -O3 for the following code:
a) what does this have to do with the kernel?
b) it is not a compiler bug, read info gcc about strict-aliasing
Jakub
prev parent reply other threads:[~2001-09-07 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 11:04 epic100.c, SMC EtherPower II, SMC83c170/175 "EPIC" Ingo Rohloff
2001-09-07 14:01 ` Ingo Rohloff
2001-09-07 14:03 ` epic100.c, gcc-2.95.2 compiler bug! Ingo Rohloff
2001-09-07 14:13 ` antirez
2001-09-07 14:26 ` Jakub Jelinek [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=20010907102602.J25384@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=antirez@invece.org \
--cc=linux-kernel@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.