public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: corrado.giacomini@trema.com
To: gcc-gnats@gcc.gnu.org
Cc: harri.pasanen@trema.com
Subject: optimization/6856: -O2 options causes Internal compiler error on hpux11.00
Date: Wed, 29 May 2002 05:16:00 -0000	[thread overview]
Message-ID: <20020529120425.22338.qmail@sources.redhat.com> (raw)


>Number:         6856
>Category:       optimization
>Synopsis:       -O2 options causes Internal compiler error on hpux11.00
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed May 29 05:06:03 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Corrado Giacomini
>Release:        gcc version 3.1.1 20020517 (prerelease)
>Organization:
>Environment:
hppa2.0w-hp-hpux11.00
>Description:
In compiling the test.cc file using optimization options
I have the following error message, while compile properly if I take off the -O2 options.

The same code compile well in both cases on linux and 
on hpux as well using KCC compiler.

g++ -c -O2 test.cc
test.cc: In function `void __static_initialization_and_destruction_0(int,
   int)':
test.cc:16: Internal compiler error in simplify_gen_subreg, at simplify-rtx.c:
   2711
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>How-To-Repeat:
Compile the attached test file using the following options:
g++ -c -O2  test.c
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="test.ii"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="test.ii"

IyAxICJ0ZXN0LmNjIgojIDEgIjxidWlsdC1pbj4iCiMgMSAiPGNvbW1hbmQgbGluZT4iCiMgMSAi
dGVzdC5jYyIKY2xhc3MgQSB7CnB1YmxpYzoKICBpbmxpbmUgQShjb25zdCBjaGFyKmNvbnN0KiB1
c2VyX2V4Y25zKSB7fQogIHZpcnR1YWwgfkEoKSB7fQp9OwoKc3RhdGljIGNvbnN0IGNoYXIqIF9Q
RF9yZXBvSWQgPSAiIEJMQSBCTEEgIjsKCmNsYXNzIEIgOiBwdWJsaWMgQQp7CnB1YmxpYzoKICBp
bmxpbmUgQigpOiBBKF91c2VyX2V4bnMpIHt9CiAgc3RhdGljIGNvbnN0IGNoYXIqIGNvbnN0IF91
c2VyX2V4bnNbXTsKfTsKCmNvbnN0IGNoYXIqIGNvbnN0IEI6Ol91c2VyX2V4bnNbXSA9IHsKICBf
UERfcmVwb0lkCn07Cg==


             reply	other threads:[~2002-05-29 12:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29  5:16 corrado.giacomini [this message]
2002-07-29  9:16 Steve Ellcey
2003-02-19 10:13 ebotcazou
2003-02-19 16:36 Steve Ellcey
2003-02-19 16:46 Eric Botcazou
2003-02-19 16:56 Steve Ellcey
2003-02-19 17:46 Corrado Giacomini
2003-05-07  8:36 Dara Hazeghi
2003-05-07 10:13 giovannibajo

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=20020529120425.22338.qmail@sources.redhat.com \
    --to=corrado.giacomini@trema.com \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=harri.pasanen@trema.com \
    /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).