public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hvreddy1110 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/17810] [3.4 Regression] internal compiler error: in verify_local_live_at_start for arm-rtems, arm-linux
Date: Tue, 22 Aug 2006 14:28:00 -0000 [thread overview]
Message-ID: <20060822142832.26293.qmail@sourceware.org> (raw)
In-Reply-To: <bug-17810-9414@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from hvreddy1110 at gmail dot com 2006-08-22 14:28 -------
Hi,
I used and Xfree86-4.4 and 4.5 with gcc-3.4.3
But both the time it is giving same problem as
slicer.cc: In function `void triangulateRect(Arc*, Backend&, int, int, int)':
slicer.cc:382: internal compiler error: in verify_local_live_at_start, at
flow.c:546
What could be the problem.
Thanks
Regards,
Harsha
(In reply to comment #5)
> http://sources.redhat.com/ml/crossgcc/2005-05/msg00154.html
> is a report of a similar problem with
> gcc-3.4.3. xfree86-4.5.0's fontutils.c causes an ICE when
> compiled with -O3 -fno-strict-aliasing. Backing down to xfree86-4.4.0,
> or using -O2, or not using -no-strict-aliasing, or using gcc-4.0.0,
> makes the problem go away. I'll attach a reduced testcase.
> To reproduce, do
> $ arm-unknown-linux-gnu-gcc -O3 -fno-strict-aliasing -c fontutils.i
> Error is
> fontutils.i:44: internal compiler error: in verify_local_live_at_start, at
> flow.c:546
>
> Is this the same problem, or should I file a new report?
--
hvreddy1110 at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hvreddy1110 at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17810
next parent reply other threads:[~2006-08-22 14:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-17810-9414@http.gcc.gnu.org/bugzilla/>
2006-08-22 14:28 ` hvreddy1110 at gmail dot com [this message]
2006-08-22 15:17 ` pinskia at gcc dot gnu dot org
2004-10-03 13:54 [Bug c/17810] New: " pisa at cmp dot felk dot cvut dot cz
2004-12-06 23:53 ` [Bug rtl-optimization/17810] [3.4 Regression] " belyshev at lubercy dot com
2005-02-01 19:13 ` joel at gcc dot gnu dot org
2005-03-11 12:45 ` buytenh at wantstofly dot org
2005-05-19 17:50 ` mmitchel at gcc dot gnu dot org
2005-05-20 18:05 ` dank at kegel dot com
2005-09-01 13:09 ` cvs-commit at gcc dot gnu dot org
2005-09-01 13:14 ` rearnsha at gcc dot gnu dot org
2005-09-01 14:55 ` cvs-commit 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=20060822142832.26293.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).