public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bkorb at gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/30678] sysmacros.h get currupt from Fixincludes with updated glibc. Date: Sat, 03 Feb 2007 18:32:00 -0000 [thread overview] Message-ID: <20070203183236.26381.qmail@sourceware.org> (raw) In-Reply-To: <bug-30678-13681@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from bkorb at gnu dot org 2007-02-03 18:32 ------- I'm looking at the inclhack fix now: > fix = { > hackname = glibc_c99_inline_4; > files = sys/sysmacros.h, '*/sys/sysmacros.h'; > bypass = "__STDC_VERSION__"; > c_fix = format; > c_fix_arg = "\n#if __STDC_VERSION__ < 19901L\nextern\n#endif\n"; > c_fix_arg = "extern"; > test_text = <<-EOT > __extension__ extern __inline unsigned int > EOT; > }; Unfortunately, there is no commentary about intended purpose and the current discussion does not explain exactly what is needed. I am going to take a guess that the __extern_inline macro will not ever need this special treatment. Therefore, the fix should look like the following. Comments, please? > fix = { > hackname = glibc_c99_inline_4; > files = sys/sysmacros.h, '*/sys/sysmacros.h'; > bypass = "__STDC_VERSION__"; > select = ' extern '; > c_fix = format; > c_fix_arg = "\n#if __STDC_VERSION__ < 19901L\nextern\n#endif\n"; > test_text = <<-EOT > __extension__ extern __inline unsigned int > EOT; > }; -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30678
next prev parent reply other threads:[~2007-02-03 18:32 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-02 9:34 [Bug bootstrap/30678] New: " ron3763 at msn dot com 2007-02-02 10:39 ` [Bug bootstrap/30678] " franke dot daniel at gmail dot com 2007-02-02 14:57 ` bkorb at gnu dot org 2007-02-02 21:22 ` ron3763 at msn dot com 2007-02-02 21:32 ` bkorb at gnu dot org 2007-02-03 18:32 ` bkorb at gnu dot org [this message] 2007-02-03 19:33 ` ron3763 at msn dot com 2007-02-03 20:37 ` bkorb at gnu dot org 2007-02-04 11:32 ` ron3763 at msn dot com 2007-02-04 22:24 ` tkoenig at gcc dot gnu dot org 2007-02-04 23:06 ` ron3763 at msn dot com 2007-02-04 23:07 ` ron3763 at msn dot com 2007-02-07 20:05 ` [Bug bootstrap/30678] [4.3 regression] " tkoenig at gcc dot gnu dot org 2007-02-07 21:02 ` bkorb at gnu dot org 2007-02-08 20:26 ` tkoenig at gcc dot gnu dot org 2007-02-08 20:53 ` bkorb at gnu dot org 2007-02-08 21:38 ` pinskia at gcc dot gnu dot org 2007-02-09 21:45 ` pinskia at gcc dot gnu dot org 2007-03-01 5:08 ` b33fc0d3 at gmail dot com
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=20070203183236.26381.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: 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).