public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: stefan@space.twc.de
To: gcc-gnats@gcc.gnu.org
Subject: c++/9630: crash with -freg-struct-return in C++ code
Date: Sat, 08 Feb 2003 21:36:00 -0000	[thread overview]
Message-ID: <20030208213433.30203.qmail@sources.redhat.com> (raw)


>Number:         9630
>Category:       c++
>Synopsis:       crash with -freg-struct-return in C++ code
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Feb 08 21:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     stefan@space.twc.de
>Release:        gcc-3.2.2
>Organization:
>Environment:
Debian unstable on i386
>Description:
    Hi!

The attached code compiles and runs with gcc-3.2.2 and compiles and crashes when compiled with gcc-3.2.2 with the -freg-struct-return option. I think this is a compiler bug.

    Cu... Stefan
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-c++src; name="reg-struct-return-testcase.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="reg-struct-return-testcase.cc"

LyoKICogVGVzdGNhc2UgZm9yIHdyb25nIGNvbXBpbGVyIGJlaGF2aW91ciAodmFsaWQgQysrIGNv
ZGUgc2VnZmF1bHRzKSB3aGVuIHVzaW5nIC1mcmVnLXN0cnVjdC1yZXR1cm4KICogaW4gY29uanVu
Y3Rpb24gd2l0aCBDKysgc291cmNlczoKICoKICogc3RlZmFuQGRlYmlhbjp+L3NyYy9iZWFzdC9z
ZmkkIGcrKyAtbyB4IHguY2MgICYmIC4veAogKiAyCiAqIHN0ZWZhbkBkZWJpYW46fi9zcmMvYmVh
c3Qvc2ZpJCBnKysgLW8geCB4LmNjIC1mcmVnLXN0cnVjdC1yZXR1cm4gJiYgLi94CiAqIFNwZWlj
aGVyenVncmlmZnNmZWhsZXIKICogc3RlZmFuQGRlYmlhbjp+L3NyYy9iZWFzdC9zZmkkIGcrKyAt
dgogKiBSZWFkaW5nIHNwZWNzIGZyb20gL3Vzci9saWIvZ2NjLWxpYi9pMzg2LWxpbnV4LzMuMi4y
L3NwZWNzCiAqIENvbmZpZ3VyZWQgd2l0aDogLi4vc3JjL2NvbmZpZ3VyZSAtdiAtLWVuYWJsZS1s
YW5ndWFnZXM9YyxjKyssamF2YSxmNzcscHJvdG8scGFzY2FsLG9iamMsYWRhIC0tcHJlZml4PS91
c3IgLS1tYW5kaXI9L3Vzci9zaGFyZS9tYW4gLS1pbmZvZGlyPS91c3Ivc2hhcmUvaW5mbyAtLXdp
dGgtZ3h4LWluY2x1ZGUtZGlyPS91c3IvaW5jbHVkZS9jKysvMy4yIC0tZW5hYmxlLXNoYXJlZCAt
LXdpdGgtc3lzdGVtLXpsaWIgLS1lbmFibGUtbmxzIC0td2l0aG91dC1pbmNsdWRlZC1nZXR0ZXh0
IC0tZGlzYWJsZS1fX2N4YV9hdGV4aXQgLS1lbmFibGUtamF2YS1nYz1ib2VobSAtLWVuYWJsZS1v
YmpjLWdjIGkzODYtbGludXgKICogVGhyZWFkIG1vZGVsOiBwb3NpeAogKiBnY2MgdmVyc2lvbiAz
LjIuMiAyMDAzMDEzMSAoRGViaWFuIHByZXJlbGVhc2UpCiAqLwoKI2luY2x1ZGUgPHN0cmluZz4K
I2luY2x1ZGUgPHN0ZGlvLmg+Cgp1c2luZyBuYW1lc3BhY2Ugc3RkOwoKaW50IGNvdW50Q29sb25z
IChjb25zdCBzdHJpbmcmIG5hbWUpCnsKICBpbnQgY29sb25zID0gMDsKCiAgZm9yKHN0cmluZzo6
Y29uc3RfaXRlcmF0b3IgaSA9IG5hbWUuYmVnaW4oKTsgaSAhPSBuYW1lLmVuZCgpOyBpKyspCiAg
ICB7CiAgICAgIGlmICgqaSA9PSAnOicpCgljb2xvbnMrKzsKICAgIH0KICByZXR1cm4gY29sb25z
Owp9CgppbnQgbWFpbigpCnsKICBwcmludGYgKCIlZFxuIiwgY291bnRDb2xvbnMgKCJUZXN0OjpG
b3JTZWdmYXVsdCIpKTsKfQoKLyogdmltOnNldCB0cz04IHN3PTIgc3RzPTI6ICovCg==


                 reply	other threads:[~2003-02-08 21:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030208213433.30203.qmail@sources.redhat.com \
    --to=stefan@space.twc.de \
    --cc=gcc-gnats@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).