public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "antoine.balestrat at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/58011] New: GCC segfaults at -O1
Date: Sun, 28 Jul 2013 10:32:00 -0000 [thread overview]
Message-ID: <bug-58011-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58011
Bug ID: 58011
Summary: GCC segfaults at -O1
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: antoine.balestrat at gmail dot com
Using GCC 4.9.0 as of 20130728 :
$ cat seg.c
int a, b;
void f(unsigned p)
{
unsigned *pp = &p;
if(!a)
p = 0;
for(b = 0; b < 1; b++)
if(3 * p + 5 * *pp)
a = 0;
}
$ xgcc -O1 seg.c
seg.c: In function ‘f’:
seg.c:3:6: internal compiler error: Segmentation fault
void f(unsigned p)
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
>From gcc-bugs-return-426863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 28 11:05:06 2013
Return-Path: <gcc-bugs-return-426863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31924 invoked by alias); 28 Jul 2013 11:05:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31840 invoked by uid 48); 28 Jul 2013 11:05:03 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/58009] Elements with same value in vector subscript in variable definition context
Date: Sun, 28 Jul 2013 11:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-58009-4-dvmYj8zoOl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58009-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58009-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-07/txt/msg01370.txt.bz2
Content-length: 254
http://gcc.gnu.org/bugzilla/show_bug.cgi?idX009
--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
I also want to catch
a([i,j,i]) = ...
for which I cannot think of an algorithm which is O(n),
so I guess it will have to be O(n**2).
next reply other threads:[~2013-07-28 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-28 10:32 antoine.balestrat at gmail dot com [this message]
2013-07-28 19:35 ` [Bug tree-optimization/58011] " olegendo at gcc dot gnu.org
2013-09-04 17:48 ` eraman at gcc dot gnu.org
2014-02-28 9:01 ` olegendo at gcc dot gnu.org
2014-03-13 19:59 ` olegendo at gcc dot gnu.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=bug-58011-4@http.gcc.gnu.org/bugzilla/ \
--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).