public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/20297] #pragma GCC visibility isn't properly handled for builtin functions
Date: Wed, 22 Mar 2006 04:55:00 -0000	[thread overview]
Message-ID: <20060322045522.11572.qmail@sourceware.org> (raw)
In-Reply-To: <bug-20297-682@http.gcc.gnu.org/bugzilla/>



------- Comment #18 from jason at gcc dot gnu dot org  2006-03-22 04:55 -------
Subject: Bug 20297

Author: jason
Date: Wed Mar 22 04:55:18 2006
New Revision: 112274

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=112274
Log:
        PR middle-end/20297
        * expr.c (init_block_move_fn): Force default visibility.
        (init_block_clear_fn): Likewise.

Modified:
    branches/redhat/gcc-3_4-branch/gcc/ChangeLog
    branches/redhat/gcc-3_4-branch/gcc/expr.c


-- 


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


  parent reply	other threads:[~2006-03-22  4:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-20297-682@http.gcc.gnu.org/bugzilla/>
2005-10-18 12:21 ` simon dot strandman at telia dot com
2005-12-05  5:38 ` zac at zacbowling dot com
2006-01-27 12:24 ` bero at arklinux dot org
2006-03-22  3:33 ` jason at gcc dot gnu dot org
2006-03-22  4:21 ` jason at gcc dot gnu dot org
2006-03-22  4:22 ` jason at gcc dot gnu dot org
2006-03-22  4:23 ` jason at gcc dot gnu dot org
2006-03-22  4:50 ` jason at gcc dot gnu dot org
2006-03-22  4:55 ` jason at gcc dot gnu dot org [this message]
2006-06-23  1:11 ` jason at gcc dot gnu dot org
2005-03-03  0:02 [Bug middle-end/20297] New: " hjl at lucon dot org
2005-03-03  0:05 ` [Bug middle-end/20297] " hjl at lucon dot org
2005-03-03 19:03 ` bugzilla at mdaniel dot scdi dot com
2005-03-03 19:06 ` pinskia at gcc dot gnu dot org
2005-03-03 19:11 ` hjl at lucon dot org
2005-03-03 19:19 ` bugzilla at mdaniel dot scdi dot com
2005-03-03 19:25 ` hjl at lucon dot org
2005-05-23  9:53 ` matz at suse dot de
2005-05-23 10:06 ` pluto at agmk dot net
2005-05-26 14:45 ` pluto at agmk dot net
2005-06-06  7:48 ` matz at suse dot de
2005-09-09 20:51 ` benjamin at smedbergs dot us
2005-09-13 16:34 ` benjamin at smedbergs dot us
2005-09-13 16:34 ` benjamin at smedbergs dot us

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=20060322045522.11572.qmail@sourceware.org \
    --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).