public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/7464: weak symbols alias definitions are broken in 3.1.1 (weak alias regression from 2.95) Date: Fri, 25 Oct 2002 07:16:00 -0000 [thread overview] Message-ID: <20021025141601.2331.qmail@sources.redhat.com> (raw) The following reply was made to PR c/7464; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gcc@gcc.gnu.org, <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: c/7464: weak symbols alias definitions are broken in 3.1.1 (weak alias regression from 2.95) Date: Fri, 25 Oct 2002 09:08:25 -0500 (CDT) This is one more regression from 2.95 with respect to weak and alias attributes: -------------------------------------------------- extern int i __attribute__ ((alias ("__i"))); extern int i __attribute__ ((weak, alias ("__i"))); -------------------------------------------------- In contrast to c++/6074, which is similar but treats functions instead of variables, this is broken in both C and C++, and is also not fixed on mainline. The messages I get are: from C: x.c:2: error: weak declaration of `i' must precede definition from C++: x.cc:2: error: redefinition of `int i' x.cc:1: error: `int i' previously declared here As said, gcc2.95 accepts this. Regards Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-10-25 14:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-25 7:16 Wolfgang Bangerth [this message] 2002-10-25 7:36 Andreas Jaeger 2002-10-25 7:46 Wolfgang Bangerth 2002-10-25 11:26 Richard Henderson
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=20021025141601.2331.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).