public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault in record_one_conflict, ra-conflict.c:176
Date: Thu, 08 Jan 2009 22:23:00 -0000	[thread overview]
Message-ID: <20090108222313.27681.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38666-13529@http.gcc.gnu.org/bugzilla/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]



------- Comment #16 from hjl dot tools at gmail dot com  2009-01-08 22:23 -------
(In reply to comment #15)
> This is fixed in 4.4 by IRA:
> 
> gnu-3:pts/0[29]> ./xgcc -B./ -O -S /net/gnu-6/export/home/hjl/tmp/gcc_bug.i
> -fno-ira
> gcc_bug.c: In function ‘main’:
> gcc_bug.c:23030: internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://gcc.gnu.org/bugs.html> for instructions.
> gnu-3:pts/0[30]>
> "
> 
> part, i.e. on the one hand there is a statement that the problem is fixed in
> 4.4, on the other hand the example still shows "internal compiler error:
> Segmentation fault" - is this example from 4.4 ?
> 
> If yes, how does "Segmentation fault" indicate that the problem is fixed ?
> 

You only see "Segmentation fault" with -fno-ira.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38666


  parent reply	other threads:[~2009-01-08 22:23 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29 22:21 [Bug c/38666] New: internal compiler error: Segmentation fault sergstesh at yahoo dot com
2008-12-29 22:56 ` [Bug c/38666] " sergstesh at yahoo dot com
2008-12-29 22:56 ` sergstesh at yahoo dot com
2008-12-29 23:01 ` sergstesh at yahoo dot com
2008-12-29 23:27 ` [Bug middle-end/38666] " pinskia at gcc dot gnu dot org
2008-12-29 23:38 ` [Bug c/38666] " sergstesh at yahoo dot com
2008-12-29 23:41 ` [Bug middle-end/38666] " pinskia at gcc dot gnu dot org
2008-12-29 23:45 ` rguenth at gcc dot gnu dot org
2008-12-30  0:01 ` [Bug c/38666] " sergstesh at yahoo dot com
2008-12-30  0:04 ` [Bug middle-end/38666] " pinskia at gcc dot gnu dot org
2008-12-30  0:10 ` [Bug c/38666] " sergstesh at yahoo dot com
2008-12-30 10:18 ` rguenth at gcc dot gnu dot org
2009-01-02 20:24 ` [Bug middle-end/38666] " pinskia at gcc dot gnu dot org
2009-01-08 13:03 ` [Bug middle-end/38666] [4.3 Regression] " ubizjak at gmail dot com
2009-01-08 13:11 ` ubizjak at gmail dot com
2009-01-08 13:55 ` ubizjak at gmail dot com
2009-01-08 18:30 ` [Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault in record_one_conflict, ra-conflict.c:176 hjl dot tools at gmail dot com
2009-01-08 20:04 ` hjl dot tools at gmail dot com
2009-01-08 22:18 ` sergstesh at yahoo dot com
2009-01-08 22:23 ` hjl dot tools at gmail dot com [this message]
2009-01-08 22:26 ` sergstesh at yahoo dot com
2009-01-08 23:03 ` rguenth at gcc dot gnu dot org
2009-01-09  7:21 ` ubizjak at gmail dot com
2009-01-21 22:14 ` rguenth at gcc dot gnu dot org
2009-01-24 10:40 ` rguenth at gcc dot gnu dot org
2009-08-04 12:46 ` rguenth at gcc dot gnu dot org
2010-05-22 18:28 ` rguenth at gcc dot gnu dot org
2010-05-23  4:49 ` sergstesh at yahoo dot com
2010-05-24 12:56 ` rguenth at gcc dot gnu dot org
     [not found] <bug-38666-4@http.gcc.gnu.org/bugzilla/>
2011-06-27 11:55 ` rguenth 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=20090108222313.27681.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).