This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug string/20736] string2.h strcmp macro gratuitously adds __builtin_
- From: "acsawdey at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 27 Oct 2016 16:20:28 +0000
- Subject: [Bug string/20736] string2.h strcmp macro gratuitously adds __builtin_
- Auto-submitted: auto-generated
- References: <bug-20736-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20736
--- Comment #2 from Aaron Sawdey <acsawdey at gcc dot gnu.org> ---
I opened this bug because of the asymmetry between strncmp's macro that just
expands in terms of strncmp, and the strcmp macro that expands to
__builtin_strcmp. I can live with having to have a more complex workaround if I
want to disable the expansion of __builtin_strcmp that I'm adding to gcc.
The questions I suppose I was trying to ask are: why is there a difference
between what these two macros do in this regard? Why does the strcmp macro feel
it cannot leave the decision of what to do with the strcmp function call up to
the compiler (i.e. expand builtin or don't)?
If the answer is that the status quo is ok, I can live with that.
Thanks,
Aaron
--
You are receiving this mail because:
You are on the CC list for the bug.