public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/31309] 6 byte assignment at end of structure reads/writes past end of structure causing SEGV when that memory is not accessable.
Date: Fri, 06 Jul 2007 15:45:00 -0000 [thread overview]
Message-ID: <20070706154513.6563.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31309-12838@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from rguenth at gcc dot gnu dot org 2007-07-06 15:45 -------
This is also a missed optimization ;)
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|target |middle-end
GCC build triplet|x86_64-unknown-linux-gnu |
GCC host triplet|x86_64-unknown-linux-gnu |
Keywords| |missed-optimization
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31309
next prev parent reply other threads:[~2007-07-06 15:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 4:24 [Bug c++/31309] New: g++ 4.2.0 amd64 codegen issue with -O0. " peeterj at ca dot ibm dot com
2007-03-22 4:28 ` [Bug c++/31309] " peeterj at ca dot ibm dot com
2007-03-22 10:03 ` rguenth at gcc dot gnu dot org
2007-03-22 15:50 ` taavib at ca dot ibm dot com
2007-06-27 14:49 ` peeterj at ca dot ibm dot com
2007-07-06 13:54 ` [Bug middle-end/31309] [4.1/4.2/4.3 Regression] " rguenth at gcc dot gnu dot org
2007-07-06 14:05 ` rguenth at gcc dot gnu dot org
2007-07-06 14:59 ` rguenth at gcc dot gnu dot org
2007-07-06 15:06 ` [Bug target/31309] " rguenth at gcc dot gnu dot org
2007-07-06 15:42 ` matz at gcc dot gnu dot org
2007-07-06 15:45 ` rguenth at gcc dot gnu dot org [this message]
2008-01-02 23:18 ` [Bug middle-end/31309] " peeterj at ca dot ibm dot com
2008-01-03 9:11 ` rguenth at gcc dot gnu dot org
2008-01-03 15:39 ` peeterj at ca dot ibm dot com
2008-01-03 17:30 ` rguenth at gcc dot gnu dot org
2008-01-03 17:35 ` rguenth at gcc dot gnu dot org
2008-01-03 22:00 ` ebotcazou at gcc dot gnu dot org
2008-01-08 17:25 ` ebotcazou at gcc dot gnu dot org
2008-01-09 10:35 ` matz at gcc dot gnu dot org
2008-01-09 12:15 ` ebotcazou at gcc dot gnu dot org
2008-01-11 20:28 ` [Bug middle-end/31309] [4.1/4.2/4.3 regression] reads/writes past end of structure ebotcazou at gcc dot gnu dot org
2008-01-11 20:30 ` [Bug middle-end/31309] [4.1/4.2 " ebotcazou at gcc dot gnu dot org
2008-01-16 1:49 ` peeterj at ca dot ibm dot com
2008-01-16 12:57 ` ebotcazou at gcc dot gnu dot org
2008-01-17 15:43 ` ebotcazou at gcc dot gnu dot org
2008-01-17 15:48 ` [Bug middle-end/31309] [4.1 " ebotcazou at gcc dot gnu dot org
2008-01-21 20:09 ` ebotcazou at gcc dot gnu dot org
2008-01-21 20:10 ` ebotcazou at gcc dot gnu dot org
2008-01-21 20:17 ` peeterj at ca dot ibm dot com
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=20070706154513.6563.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).