public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/17266] Always defining __extern_always_inline may generate infinite recursion Date: Thu, 14 Aug 2014 16:45:00 -0000 [thread overview] Message-ID: <bug-17266-131-ade5dw6KTi@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17266-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17266 --- Comment #2 from Andreas Schwab <schwab@linux-m68k.org> --- It has been undone by <http://sourceware.org/ml/glibc-cvs/2007-q3/msg00912.html>. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-08-14 16:45 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-14 0:34 [Bug libc/17266] New: " siddhesh at redhat dot com 2014-08-14 11:45 ` [Bug libc/17266] " jakub at redhat dot com 2014-08-14 16:45 ` schwab@linux-m68k.org [this message] 2014-08-14 16:50 ` jakub at redhat dot com 2014-09-16 8:41 ` cvs-commit at gcc dot gnu.org 2014-09-16 8:46 ` cvs-commit at gcc dot gnu.org 2014-09-16 8:47 ` siddhesh at redhat dot com 2014-09-16 16:56 ` cvs-commit at gcc dot gnu.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=bug-17266-131-ade5dw6KTi@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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).