https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89043
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89043
--- Comment #7 from Eric Gallager ---
Anyways my point about bringing up which standards stpcpy() is in is to remind
people to keep portability concerns in mind when doing this change. Please
check the gnulib docs on stpcpy() for specifics:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89043
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89043
--- Comment #5 from Martin Sebor ---
Ah, makes sense. I briefly wondered how stpcpy could have been "updated for
alignment with the ISO/IEC 9899:1999 standard." That's the trade-off of a 4k
monitor: it fits tons of stuff on the screen but
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89043
--- Comment #4 from joseph at codesourcery dot com ---
On Thu, 24 Jan 2019, msebor at gcc dot gnu.org wrote:
> The CHANGE HISTORY section for stpcpy says the function was first released in
> Issue 1 and derived from Issue 1 of the SVID:
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89043
--- Comment #3 from Martin Sebor ---
The CHANGE HISTORY section for stpcpy says the function was first released in
Issue 1 and derived from Issue 1 of the SVID:
http://pubs.opengroup.org/onlinepubs/9699919799/functions/stpcpy.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89043
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89043
Martin Sebor changed:
What|Removed |Added
Keywords||missed-optimization
See Also|
