public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ahs3@fc.hp.com
To: gcc-gnats@gcc.gnu.org
Cc: bobm@fc.hp.com
Subject: optimization/10280: __builtin_frame_address() broken in ia64 optimizer
Date: Mon, 31 Mar 2003 18:53:00 -0000 [thread overview]
Message-ID: <20030331182454.28822.qmail@sources.redhat.com> (raw)
>Number: 10280
>Category: optimization
>Synopsis: __builtin_frame_address() broken in ia64 optimizer
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Mar 31 18:26:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Al Stone
>Release: gcc-2.96 or gcc 3.2.3
>Organization:
>Environment:
Red Hat Advanced Server, or Debian GNU/Linux, on an ia64 processor.
>Description:
It appears that __builting_frame_address() is broken in the presence of the optimizer on ia64; this was found when compiling Linux kernel code that caused a stack overflow. When one looks at the assembler generated, it appears very odd that the alloc increases the register stack by 80 entries.
>How-To-Repeat:
Compile without -O and the sample works properly; compile with -O and it fails.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-csrc; name="bug.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="bug.c"
LyogVGhpcyBwcm9ncmFtIGlsbHVzdHJhdGVzIGFuIElBNjQgZ2NjIC1PIHByb2JsZW0gd2l0aAog
KiBfX2J1aWx0aW5fZnJhbWVfYWRkcmVzcy4gIEJlc2lkZXMgdGhlIGZ1bmN0aW9uIHJldHVybmlu
ZwogKiBhIHdyb25nIHJlc3VsdCwgdGhlIHN5bXB0b20gdGhhdCBsZWQgdG8gZGlzY292ZXJ5IHdh
cyB0aGF0IHRoZQogKiBhbGxvYyBzdGF0ZW1lbnQgZ2VuZXJhdGVkIGZvciByb3V0aW5lcyB0aGF0
IHVzZQogKiBfX2J1aWx0aW5fZnJhbWVfYWRkcmVzcyBhbGxvY2F0ZXMgYW4gdW51c3VhbGx5IGxh
cmdlIG51bWJlciBvZgogKiByZWdpc3RlcnMsIGxlYWRpbmcgdG8ga2VybmVsIHN0YWNrIG92ZXJm
bG93IGluIGtlcm5lbCBtb2R1bGVzIHRoYXQKICogdXNlZCB0aGUgZnVuY3Rpb24gaW4gYSBERUJV
RyBtYWNyby4KICoKICogQ29tcGlsZSB3aXRoIGdjYyAtTy4gIFJ1biB0byBzZWUgd3JvbmcgcmVz
dWx0LiAgQ29tcGlsZSBnY2MgLU8gLVMuCiAqIEV4YW1pbmUgYXNzZW1ibHkgb3V0cHV0IHRvIHNl
ZSByZWdpc3RlciBhbGxvY2F0aW9uIHByb2JsZW0uCiAqIEZvciBleGFtcGxlOiBhbGxvYyByMTYg
PSBhci5wZnMsIDAsIDgwLCA0LCAwCiAqCiAqIEJvYiBNb250Z29tZXJ5LCBIUCwgMjcgTWFyIDIw
MDMuCiAqLwoKI2luY2x1ZGUgPHN0ZGlvLmg+Cgp2b2lkIGZvbzModm9pZCkKewoJaW50IGFbMjBd
OwoJcHJpbnRmKCJmb28zOiAlcCAlcCAlcFxuIiwgJmFbMF0sICZhWzE5XSwKCQkJKCh1bnNpZ25l
ZCBsb25nKV9fYnVpbHRpbl9mcmFtZV9hZGRyZXNzKDApKSk7Cn0KCnZvaWQgZm9vMih2b2lkKQp7
CglpbnQgYVsyMF07CglwcmludGYoImZvbzI6ICVwICVwICVwXG4iLCAmYVswXSwgJmFbMTldLAoJ
CQkoKHVuc2lnbmVkIGxvbmcpX19idWlsdGluX2ZyYW1lX2FkZHJlc3MoMCkpKTsKCWZvbzMoKTsK
fQoKdm9pZCBmb28xKHZvaWQpCnsKCWludCBhWzIwXTsKCXByaW50ZigiZm9vMTogJXAgJXAgJXBc
biIsICZhWzBdLCAmYVsxOV0sCgkJCSgodW5zaWduZWQgbG9uZylfX2J1aWx0aW5fZnJhbWVfYWRk
cmVzcygwKSkpOwoJZm9vMigpOwp9CgptYWluKCkKewoJZm9vMSgpOwp9Cgo=
reply other threads:[~2003-03-31 18:26 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=20030331182454.28822.qmail@sources.redhat.com \
--to=ahs3@fc.hp.com \
--cc=bobm@fc.hp.com \
--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).