public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bkausbk@web.de
To: gcc-gnats@gcc.gnu.org
Subject: other/8437: GCC 3.2 don't produces builtin code for __builtin_alloca
Date: Sun, 03 Nov 2002 05:36:00 -0000	[thread overview]
Message-ID: <20021103132601.4942.qmail@sources.redhat.com> (raw)


>Number:         8437
>Category:       other
>Synopsis:       GCC 3.2 don't produces builtin code for __builtin_alloca
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          pessimizes-code
>Submitter-Id:   net
>Arrival-Date:   Sun Nov 03 05:36:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Benjamin Kalytta
>Release:        GCC 3.2
>Organization:
>Environment:
cygwin (v. 1.1.8) x86/AMD Athlon XP2200+ - Windows 2000 Prof.
>Description:
GCC don't create builtin function __builtin_alloca as builtin, but instead it creates an external definition in objectfile to __alloca (usually a libgcc libary function).

How to repeat:
#define alloca(n) __builtin_alloca((n))
int main() {
	char *p=alloca(10);
	return (int)p;
}
>How-To-Repeat:
Any of this:
gcc -c test.c
gcc -fbuiltin -fhosted -c test.c
gcc -fhosted -c test.c
gcc -fno-builtin -c test.c
>Fix:

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

TAEDAAAAAADQAAAADAAAAAAABAAudGV4dAAAAAAAAAAAAAAAMAAAAIwAAAC8AAAAAAAAAAIAAAAg
AABgLmRhdGEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAwC5ic3MAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAMBVieWD7AiD5PC4AAAAAIlF+ItF+OgAAAAA6AAAAACD
7BCJ4IlF/ItF/MnDkJCQkJAVAAAACwAAABQAGgAAAAkAAAAUAC5maWxlAAAAAAAAAP7/AABnAXRl
c3QuYwAAAAAAAAAAAAAAAF9tYWluAAAAAAAAAAEAIAACAC50ZXh0AAAAAAAAAAEAAAADASsAAAAC
AAAAAAAAAAAAAAAAAC5kYXRhAAAAAAAAAAIAAAADAQAAAAAAAAAAAAAAAAAAAAAAAC5ic3MAAAAA
AAAAAAMAAAADAQAAAAAAAAAAAAAAAAAAAAAAAF9fX21haW4AAAAAAAAAIAACAQAAAAAAAAAAAAAA
AAAAAAAAAF9fYWxsb2NhAAAAAAAAAAACAAQAAAA=


                 reply	other threads:[~2002-11-03 13: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=20021103132601.4942.qmail@sources.redhat.com \
    --to=bkausbk@web.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).