public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: wilhelm.nuesser@sap.com
To: gcc-gnats@gcc.gnu.org
Cc: thomas.hiller@compaq.com
Subject: optimization/4186: core dump in -O2 on ia32 with attached code (regression to 2.95.*)
Date: Fri, 31 Aug 2001 07:36:00 -0000	[thread overview]
Message-ID: <20010831143011.9206.qmail@sourceware.cygnus.com> (raw)

>Number:         4186
>Category:       optimization
>Synopsis:       core dump in -O2 on ia32 with attached code (regression to 2.95.*)
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Aug 31 07:36:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     wilhelm.nuesser@sap.com
>Release:        gcc version 3.0.1
>Organization:
>Environment:

Linux ia32, glibc 2.1, SuSE 7.0, RH 6.* ...
gcc -v gives:
Reading specs from /opt/gcc301/lib/gcc-lib/i686-pc-linux-gnu/3.0.1/specs
Configured with: ../gcc/gcc-3.0.1/configure --prefix=/opt/gcc301 --enable-shared
Thread model: single
gcc version 3.0.1
>Description:
Attached code gives core dumps when compiling with -O2.
Running -O1 works. Changing the struct s1 (removing an 
unused short) also works. Changing third parameter of memcpy
to int constant also works. 
>How-To-Repeat:
Compile attached code with -O2
>Fix:

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

I2luY2x1ZGUgPHN0cmluZy5oPgoKCnR5cGVkZWYgc3RydWN0IHMxIAp7CiAgICB1bnNpZ25lZCBj
aGFyICAqIGVudHJ5X3A7ICAgICAKICAgIHNob3J0ICAgICAgICAgICAgZW50cnlfbnI7ICAgIAog
ICAgc2hvcnQgICAgICAgICAgICBlbnRyeWxnOyAgCiAgICBzaG9ydCAgICAgICAgICAgIGxsZW47
ICAgICAKfQpzMTsKCgpzdGF0aWMgdm9pZCBmMSAodm9pZCAqIHRhYmRpciwgdW5zaWduZWQgY2hh
ciAqIGNvbnN0IGtleXMsCgkJCQkgIGNvbnN0IHMxICBlbnRyeV9sb2MpCnsKICBpbnQga2V5bGcg
PSAxMTsKCiAgKHZvaWQpIG1lbWNweShrZXlzLCBlbnRyeV9sb2MuZW50cnlfcCwga2V5bGcpOwp9
CgoKaW50IG1haW4oKQp7CiAgdm9pZCAgICAgICAgICAgICAgICAgICogdGFiZGlyOwogIHVuc2ln
bmVkIGNoYXIgICAgICAgICAqIGtleXM7CiAgczEgICAgICAgICAgICAgICAgICAgICAgZW50cnlf
bG9jOwoKICAvKiBidWlsZCB1cCAqLwogIGtleXMgPSAodW5zaWduZWQgY2hhciopIG1hbGxvYygx
MSk7CiAKICBlbnRyeV9sb2MuZW50cnlfcCA9ICh1bnNpZ25lZCBjaGFyICopIG1hbGxvYygxMSk7
CiAgbWVtc2V0KGVudHJ5X2xvYy5lbnRyeV9wLCAnQScsIDExKTsKCiAgZjEodGFiZGlyLCBrZXlz
LCBlbnRyeV9sb2MpOyAKICAKICByZXR1cm4gKDApOwp9Cg==


             reply	other threads:[~2001-08-31  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-31  7:36 wilhelm.nuesser [this message]
2001-09-24 12:46 wilson
2001-12-11 21:38 rodrigc
2001-12-11 21:46 rodrigc

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=20010831143011.9206.qmail@sourceware.cygnus.com \
    --to=wilhelm.nuesser@sap.com \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=thomas.hiller@compaq.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).