public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jparmele at wildbear dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/18052] Symbol clash with preprocessor __i686 produces segfaults.
Date: Wed, 04 Mar 2015 14:07:00 -0000 [thread overview]
Message-ID: <bug-18052-131-frkdpzTG5Y@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18052-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18052
--- Comment #6 from jparmele at wildbear dot com ---
On Wed, 4 Mar 2015, schwab@linux-m68k.org wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=18052
>
> --- Comment #5 from Andreas Schwab <schwab@linux-m68k.org> ---
> This is about as unspecific as it can get. The only certain aspect of your
> report is that your patch is wrong.
>
> --
> You are receiving this mail because:
> You reported the bug.
>
Did you intend that __i686 be a structure? That is what
# define GET_PC_THUNK_STR(reg) "__i686.get_pc_thunk." #reg
tells the compiler. The patch is misnamed; it's not just about assembly
because this appears in a header file sysdep.h.
Joseph
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-03-04 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 22:53 [Bug libc/18052] New: " jparmele at wildbear dot com
2015-02-27 23:13 ` [Bug libc/18052] " joseph at codesourcery dot com
2015-02-28 0:23 ` jparmele at wildbear dot com
2015-03-02 10:00 ` schwab@linux-m68k.org
2015-03-02 10:02 ` schwab@linux-m68k.org
2015-03-04 1:38 ` jparmele at wildbear dot com
2015-03-04 10:04 ` schwab@linux-m68k.org
2015-03-04 14:07 ` jparmele at wildbear dot com [this message]
2015-03-04 14:12 ` schwab@linux-m68k.org
2015-08-24 9:50 ` jsm28 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-18052-131-frkdpzTG5Y@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: 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).