public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/11498] [3.3/3.4 Regression] asm can't be used to give a variable its own name Date: Thu, 17 Jul 2003 21:53:00 -0000 [thread overview] Message-ID: <20030717215301.16794.qmail@sources.redhat.com> (raw) In-Reply-To: <20030711080206.11498.geoffk@gcc.gnu.org> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11498 ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2003-07-17 21:52 ------- Subject: Bug 11498 CVSROOT: /cvs/gcc Module name: gcc Changes by: geoffk@gcc.gnu.org 2003-07-17 21:52:51 Modified files: gcc : ChangeLog Makefile.in c-common.h c-lang.c c-opts.c langhooks.c varasm.c gcc/objc : objc-lang.c gcc/testsuite : ChangeLog Added files: gcc/testsuite/gcc.c-torture/compile: mangle-1.c Log message: PR 11498 * Makefile.in (c-opts.o): Add $(LANGHOOKS_DEF_H). (langhooks.o): Add $(GGC_H), gt-langhooks.h. (GTFILES): Add langhooks.c. (gt-langhooks.h): New. * c-common.h (c_static_assembler_name): Prototype. * c-lang.c (LANG_HOOKS_SET_DECL_ASSEMBLER_NAME): Define. * objc/objc-lang.c (LANG_HOOKS_SET_DECL_ASSEMBLER_NAME): Define. * c-opts.c: Include langhooks-def.h. (c_static_assembler_name): New. * langhooks.c: Include ggc.h. Include gt-langhooks.h. (var_labelno): New. (lhd_set_decl_assembler_name): Give static objects with context unique names. * varasm.c (var_labelno): Delete. (make_decl_rtl): Don't change the assembler name once it's set. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.546&r2=2.547 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/Makefile.in.diff?cvsroot=gcc&r1=1.1117&r2=1.1118 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/c-common.h.diff?cvsroot=gcc&r1=1.191&r2=1.192 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/c-lang.c.diff?cvsroot=gcc&r1=1.109&r2=1.110 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/c-opts.c.diff?cvsroot=gcc&r1=1.75&r2=1.76 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/langhooks.c.diff?cvsroot=gcc&r1=1.45&r2=1.46 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/varasm.c.diff?cvsroot=gcc&r1=1.372&r2=1.373 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/objc/objc-lang.c.diff?cvsroot=gcc&r1=1.35&r2=1.36 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&r1=1.2891&r2=1.2892 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gcc.c-torture/compile/mangle-1.c.diff?cvsroot=gcc&r1=NONE&r2=1.1
next prev parent reply other threads:[~2003-07-17 21:53 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-07-11 8:02 [Bug middle-end/11498] New: " geoffk at gcc dot gnu dot org 2003-07-11 8:02 ` [Bug middle-end/11498] " geoffk at gcc dot gnu dot org 2003-07-11 10:22 ` pinskia at physics dot uc dot edu 2003-07-15 1:11 ` [Bug middle-end/11498] [3.3/3.4 Regression] " pinskia at physics dot uc dot edu 2003-07-15 13:23 ` pinskia at physics dot uc dot edu 2003-07-16 20:58 ` geoffk at gcc dot gnu dot org 2003-07-17 21:53 ` cvs-commit at gcc dot gnu dot org [this message] 2003-07-17 21:55 ` geoffk at gcc dot gnu dot org 2003-07-17 21:55 ` geoffk at gcc dot gnu dot org 2003-07-26 2:30 ` neroden at gcc dot gnu dot org
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=20030717215301.16794.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).