public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/28834] [4.0/4.1/4.2/4.3 Regression] -O3 -g crashes sometimes when using may_alias and structs
Date: Mon, 05 Feb 2007 13:52:00 -0000 [thread overview]
Message-ID: <20070205135154.2839.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28834-6528@http.gcc.gnu.org/bugzilla/>
------- Comment #20 from hp at gcc dot gnu dot org 2007-02-05 13:51 -------
I see this for cris-elf (r121581) and mmix-knuth-mmixware (r121569) too, both
mayalias-2 and -3 both at "-O3 -g" like for x86_64.
As we have this PR, I intend to XFAIL it for these ports with those options;
IIRC that's protocol.
--
hp at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hp at gcc dot gnu dot org
Last reconfirmed|2006-10-26 08:10:02 |2007-02-05 13:51:52
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28834
next prev parent reply other threads:[~2007-02-05 13:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 11:04 [Bug debug/28834] New: [4.0/4.1/4.2 " pinskia at gcc dot gnu dot org
2006-08-24 11:06 ` [Bug debug/28834] " pinskia at gcc dot gnu dot org
2006-08-24 15:50 ` pinskia at gcc dot gnu dot org
2006-08-24 23:35 ` janis at gcc dot gnu dot org
2006-08-25 1:21 ` pinskia at gcc dot gnu dot org
2006-08-25 10:39 ` rguenth at gcc dot gnu dot org
2006-08-26 23:39 ` danglin at gcc dot gnu dot org
2006-08-29 4:41 ` pinskia at gcc dot gnu dot org
2006-08-29 4:48 ` geoffk at gcc dot gnu dot org
2006-08-30 3:28 ` pinskia at gcc dot gnu dot org
2006-08-30 7:47 ` dpatel at apple dot com
2006-09-01 21:53 ` mmitchel at gcc dot gnu dot org
2006-09-02 0:02 ` pinskia at gcc dot gnu dot org
2006-09-02 5:31 ` geoffk at geoffk dot org
2006-10-07 12:56 ` rsandifo at gcc dot gnu dot org
2006-10-15 11:39 ` ebotcazou at gcc dot gnu dot org
2006-11-20 0:50 ` [Bug debug/28834] [4.0/4.1/4.2/4.3 " pinskia at gcc dot gnu dot org
2006-11-24 0:11 ` acahalan at gmail dot com
2007-02-01 8:50 ` pinskia at gcc dot gnu dot org
2007-02-03 19:36 ` gdr at gcc dot gnu dot org
2007-02-03 20:55 ` pinskia at gcc dot gnu dot org
2007-02-05 13:52 ` hp at gcc dot gnu dot org [this message]
2007-02-10 19:23 ` pinskia at gcc dot gnu dot org
2007-02-14 9:16 ` mmitchel at gcc dot gnu dot org
2007-02-20 21:50 ` rguenth at gcc dot gnu dot org
2007-02-27 21:48 ` pinskia at gcc dot gnu dot org
2007-02-27 21:54 ` [Bug debug/28834] [4.0/4.1/4.2/4.3 Regression] " schwab at suse dot de
2007-06-20 14:31 ` [Bug debug/28834] [4.0/4.1/4.2/4.3 Regression] -g crashes sometimes when using may_alias and structs (ICE in splice_child_die) pinskia at gcc dot gnu dot org
2007-07-17 12:51 ` pinskia at gcc dot gnu dot org
2007-07-29 18:00 ` tprince at computer dot org
2007-10-24 20:00 ` jason at gcc dot gnu dot org
2007-11-09 18:22 ` pinskia at gcc dot gnu dot org
2007-11-19 21:25 ` jason at gcc dot gnu dot org
2007-11-19 22:32 ` jason at gcc dot gnu dot org
2007-11-19 22:35 ` jason at gcc dot gnu dot org
2008-02-07 19:15 ` ghazi at gcc dot gnu dot org
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=20070205135154.2839.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).