public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uweigand at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/13856] [3.4/3.5 Regression] hidden support broken with builtin functions
Date: Tue, 03 Feb 2004 20:47:00 -0000	[thread overview]
Message-ID: <20040203204704.10201.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040125122814.13856.aj@gcc.gnu.org>


------- Additional Comments From uweigand at gcc dot gnu dot org  2004-02-03 20:47 -------
Sorry, I was wrong: of course this is related to builtin functions. 
 
In fact, the current behaviour is directly caused by Zack's patch 
to fix PR 18314 (http://gcc.gnu.org/ml/gcc-patches/2004-01/msg02475.html). 
 
What happens is that 
 - first, we have a builtin declaration 
 - second, we get an excplicit declaration which matches the builtin; 
   it provides new attributes that are merged into the builtin decl 
 - third, we get a K&R definition; after Zack's patch K&R definitions 
   are considered to always override the builtin decl, hence the  
   builtin decl is thrown away together with the changed attributes 
 
Is this behaviour wrong?  Is the source code valid in the first place? 
 

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13856


  parent reply	other threads:[~2004-02-03 20:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-25 12:28 [Bug c/13856] New: " aj at gcc dot gnu dot org
2004-01-25 12:29 ` [Bug c/13856] " aj at gcc dot gnu dot org
2004-01-25 12:30 ` aj at gcc dot gnu dot org
2004-01-25 15:52 ` [Bug c/13856] [3.4 Regression] " pinskia at gcc dot gnu dot org
2004-01-26  6:30 ` [Bug c/13856] [3.4/3.5 " aj at gcc dot gnu dot org
2004-02-01 13:28 ` pinskia at gcc dot gnu dot org
2004-02-03 20:19 ` uweigand at gcc dot gnu dot org
2004-02-03 20:47 ` uweigand at gcc dot gnu dot org [this message]
2004-02-03 21:25 ` zack at gcc dot gnu dot org
2004-02-08  1:52 ` cvs-commit at gcc dot gnu dot org
2004-02-08  1:54 ` zack at codesourcery dot com
2004-02-08  1:59 ` cvs-commit at gcc dot gnu dot org
2004-02-08  2:01 ` zack at gcc dot gnu dot org
2004-02-08  6:41 ` aj at suse dot de
2004-02-08  7:10 ` zack at codesourcery dot com
2004-02-08  7:25 ` gdr at integrable-solutions dot net

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=20040203204704.10201.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: 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).