public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: zack@codesourcery.com (Zack Weinberg)
To: gcc-gnats@gcc.gnu.org
Subject: c/10375: Function-local external decls of builtins don't get attributes
Date: Fri, 11 Apr 2003 02:36:00 -0000 [thread overview]
Message-ID: <20030411023452.18801.qmail@sources.redhat.com> (raw)
>Number: 10375
>Category: c
>Synopsis: Function-local external decls of builtins don't get attributes
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Apr 11 02:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: zack@codesourcery.com (Zack Weinberg)
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
GCC fails to optimize (e.g.)
extern void bar(void);
void foo() { extern void abort(void); abort(); bar(); }
when the function-local decl is the only one visible. This
is because the "anticipated" declaration is at file scope and the function-local decl is considered to shadow it.
See attached test case for more extensive tests.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="builtin-noret-2.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="builtin-noret-2.c"
LyogVGVzdCBmb3IgYnVpbHRpbiBub3JldHVybiBhdHRyaWJ1dGVzIHdoZW4gdGhlIHZpc2libGUg
ZGVjbGFyYXRpb25zCiAgIGFyZSBmdW5jdGlvbi1sb2NhbC4gIERvZXNuJ3QgcHJlc2VudGx5IHdv
cmsuICBNb2RpZmllZCBmcm9tCiAgIGJ1aWx0aW4tbm9yZXQtMS5jIGJ5IFphY2sgV2VpbmJlcmcg
PHphY2tAY29kZXNvdXJjZXJ5LmNvbT4uICAqLwoKZXh0ZXJuIHZvaWQgdGFib3J0ICh2b2lkKTsK
ZXh0ZXJuIHZvaWQgdGV4aXQgKHZvaWQpOwpleHRlcm4gdm9pZCB0X2V4aXQgKHZvaWQpOwpleHRl
cm4gdm9pZCB0X0V4aXQgKHZvaWQpOwoKZXh0ZXJuIHZvaWQgbGlua19mYWlsdXJlICh2b2lkKTsK
CmludAptYWluICh2b2lkKQp7CiAgdm9sYXRpbGUgaW50IGkgPSAwOwogIC8qIFRoZSByZWFsIHRl
c3QgaGVyZSBpcyB0aGF0IHRoZSBwcm9ncmFtIGxpbmtzLiAgKi8KICBpZiAoaSkKICAgIHRhYm9y
dCAoKTsKICBpZiAoaSkKICAgIHRleGl0ICgpOwogIGlmIChpKQogICAgdF9leGl0ICgpOwogIGlm
IChpKQogICAgdF9FeGl0ICgpOwogIGV4aXQgKDApOwp9Cgp2b2lkCnRhYm9ydCAodm9pZCkKewog
IGV4dGVybiB2b2lkIGFib3J0ICh2b2lkKTsKICBhYm9ydCAoKTsKICBsaW5rX2ZhaWx1cmUgKCk7
Cn0KCnZvaWQKdGV4aXQgKHZvaWQpCnsKICBleHRlcm4gdm9pZCBleGl0IChpbnQpOwogIGV4aXQg
KDEpOwogIGxpbmtfZmFpbHVyZSAoKTsKfQoKdm9pZAp0X2V4aXQgKHZvaWQpCnsKICBleHRlcm4g
dm9pZCBfZXhpdCAoaW50KTsKICBfZXhpdCAoMSk7CiAgbGlua19mYWlsdXJlICgpOwp9CgovKiBT
b21lIG5vbi1Vbml4IGxpYmNzIG1pZ2h0IG5vdCBoYXZlIF9leGl0LiAgVGhpcyB2ZXJzaW9uIHNo
b3VsZCBuZXZlcgogICBnZXQgY2FsbGVkLiAgKi8Kc3RhdGljIHZvaWQKX2V4aXQgKGludCBpKQp7
CiAgYWJvcnQgKCk7Cn0KCnZvaWQKdF9FeGl0ICh2b2lkKQp7CiAgZXh0ZXJuIHZvaWQgX0V4aXQg
KGludCk7CiAgX0V4aXQgKDEpOwogIGxpbmtfZmFpbHVyZSAoKTsKfQoKLyogU29tZSBsaWJjcyBt
aWdodCBub3QgaGF2ZSBfRXhpdC4gIFRoaXMgdmVyc2lvbiBzaG91bGQgbmV2ZXIgZ2V0IGNhbGxl
ZC4gICovCnN0YXRpYyB2b2lkCl9FeGl0IChpbnQgaSkKewogIGFib3J0ICgpOwp9CgovKiBXaGVu
IG9wdGltaXppbmcsIG5vIGNhbGxzIHRvIGxpbmtfZmFpbHVyZSBzaG91bGQgcmVtYWluLiAgSW4g
YW55IGNhc2UsCiAgIGxpbmtfZmFpbHVyZSBzaG91bGQgbm90IGJlIGNhbGxlZC4gICovCgojaWZu
ZGVmIF9fT1BUSU1JWkVfXwp2b2lkCmxpbmtfZmFpbHVyZSAodm9pZCkKewogIGFib3J0ICgpOwp9
CiNlbmRpZgo=
next reply other threads:[~2003-04-11 2:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 2:36 Zack Weinberg [this message]
2003-04-18 17:45 sayle
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=20030411023452.18801.qmail@sources.redhat.com \
--to=zack@codesourcery.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).