https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #51 from David Brown ---
(In reply to M Welinder from comment #48)
> It's your (1). gcc is changing a program that can rely on errno not being
> changed to one where the C library can change it. (The current C library or
> any futur
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Richard Biener changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #49 from Richard Biener ---
(In reply to M Welinder from comment #48)
> It's your (1). gcc is changing a program that can rely on errno not being
> changed to one where the C library can change it. (The current C library or
> any fu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #48 from M Welinder ---
It's your (1). gcc is changing a program that can rely on errno not being
changed to one where the C library can change it. (The current C library or
any future library that the resulting binary may be dynami
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #47 from David Brown ---
(In reply to M Welinder from comment #46)
> Should "-std=c99" imply turning off these optimizations?
>
> Creating calls to, say, strlen is incompatible with the C99 standard and
> perhaps better limited to "-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #46 from M Welinder ---
Should "-std=c99" imply turning off these optimizations?
Creating calls to, say, strlen is incompatible with the C99 standard and
perhaps better limited to "-std=gnu-something" or an opt-in f-flag.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Andrew Pinski changed:
What|Removed |Added
CC||michael.meier at hexagon dot
com
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Andrew Pinski changed:
What|Removed |Added
CC||hiraditya at msn dot com
--- Comment #44
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Andrew Pinski changed:
What|Removed |Added
CC||rafael_andreas at hotmail dot
com
--- C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #42 from Eric Gallager ---
(In reply to Rich Felker from comment #41)
> > Josef Wolf mentioned that he ran into this on the gcc-help mailing list
> > here: https://gcc.gnu.org/ml/gcc-help/2019-10/msg00079.html
>
> I don't think that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #41 from Rich Felker ---
> Josef Wolf mentioned that he ran into this on the gcc-help mailing list here:
> https://gcc.gnu.org/ml/gcc-help/2019-10/msg00079.html
I don't think that's an instance of this issue. It's normal/expected th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #40 from Eric Gallager ---
Josef Wolf mentioned that he ran into this on the gcc-help mailing list here:
https://gcc.gnu.org/ml/gcc-help/2019-10/msg00079.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #38 from Marc Glisse ---
*** Bug 82845 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Marc Glisse changed:
What|Removed |Added
CC||david at westcontrol dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Richard Biener changed:
What|Removed |Added
CC||knakahara at netbsd dot org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Evan Langlois changed:
What|Removed |Added
CC||fd935653 at opayq dot com
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #33 from Jakub Jelinek ---
Yeah, I'd say we could document that gcc doesn't support any implementations
where memcpy/memmove/memset clobber errno.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #32 from rguenther at suse dot de ---
On Fri, 6 Jun 2014, terra at gnome dot org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
>
> M Welinder changed:
>
>What|Removed |Added
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
M Welinder changed:
What|Removed |Added
CC||terra at gnome dot org
--- Comment #31 from
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #30 from Richard Biener ---
Thus, from 4.8.3, 4.9.1 and 4.10.0 on -ffreestanding, -fno-hosted and
-fno-builtin
will cause -ftree-loop-distribute-patterns to _not_ be enabled by default
with -O3+ (you can still enable it manually).
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #29 from Richard Biener ---
(In reply to Rich Felker from comment #28)
> On Tue, Apr 29, 2014 at 02:16:38PM +, rguenth at gcc dot gnu.org wrote:
> > Honza, is there a more "fancy" way of doing this?
>
> The only correct way to fix
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #28 from Rich Felker ---
On Tue, Apr 29, 2014 at 02:16:38PM +, rguenth at gcc dot gnu.org wrote:
> Honza, is there a more "fancy" way of doing this?
The only correct way to fix this is to honor -ffreestanding and never
generate re
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Richard Biener changed:
What|Removed |Added
CC||hubicka at gcc dot gnu.org
--- Comment #
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #26 from Richard Biener ---
(In reply to Janosch Rux from comment #24)
> When upgrading our build environment we ran into this. We worked around the
> way mentioned in the comments.
>
> No Problems with: 4.6.3
> Broken with: 4.8.2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Richard Biener changed:
What|Removed |Added
CC||exmortis at yandex dot ru
--- Comment #2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Janosch Rux changed:
What|Removed |Added
CC||janosch.rux at web dot de
--- Comment #24 f
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #23 from rguenther at suse dot de ---
On Wed, 2 Oct 2013, bernd.edlinger at hotmail dot de wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
>
> --- Comment #22 from Bernd Edlinger ---
> (In reply to Richard Biener from com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #22 from Bernd Edlinger ---
(In reply to Richard Biener from comment #21)
> -fno-tree-loop-distribute-patterns is the reliable way to not transform loops
> into library calls.
Thanks!
Adding this fixed the generated code:
#pragma GC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
--- Comment #
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Bernd Edlinger changed:
What|Removed |Added
CC||bernd.edlinger at hotmail dot
de
--- Co
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Rich Felker changed:
What|Removed |Added
CC||bugdal at aerifal dot cx
--- Comment #19 fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #18 from Paulo J. Matos ---
I notice(In reply to Brooks Moses from comment #12)
>
> Now, if this replacement still happens when you compile with -nostdlib, that
> would be a bug since it becomes legal code in that case. But that's
>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #17 from Max Reitz ---
(In reply to Andreas Schwab from comment #16)
> That's exactly what I wrote.
Ah, okay, sorry I misunderstood.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #16 from Andreas Schwab ---
That's exactly what I wrote.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #15 from Max Reitz ---
(In reply to Andreas Schwab from comment #14)
> The relevant option is -ffreestanding, not -nostdlib.
If you're referring to me, I'll be glad to cite my OP for you :D
> Compiling the attached trivial memcpy imp
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #14 from Andreas Schwab ---
The relevant option is -ffreestanding, not -nostdlib.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #13 from Max Reitz ---
(In reply to Brooks Moses from comment #12)
> Now, if this replacement still happens when you compile with -nostdlib, that
> would be a bug since it becomes legal code in that case. But that's
> somewhat of a se
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #12 from Brooks Moses ---
(In reply to Paulo J. Matos from comment #11)
> A non-bug? If you write a memcpy function by hand and call it memcpy, gcc
> replaces the function body by a call to memcpy which generates an infinite
> loop. Ho
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #11 from Paulo J. Matos ---
(In reply to Brooks Moses from comment #10)
> Other than the documentation issues, this seems like a non-bug.
A non-bug? If you write a memcpy function by hand and call it memcpy, gcc
replaces the function
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Brooks Moses changed:
What|Removed |Added
CC||brooks at gcc dot gnu.org
--- Comment #10
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Jeff Cook changed:
What|Removed |Added
CC||j...@deseret-tech.com
--- Comment #9 from Jef
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|NEW
AssignedTo|rguenth
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #7 from Max Reitz 2013-04-09 13:20:06
UTC ---
(In reply to comment #6)
> On Tue, 9 Apr 2013, xanclic at gmail dot com wrote:
>
> >
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
> >
> > --- Comment #5 from Max Reitz 2013-0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #6 from rguenther at suse dot de
2013-04-09 13:17:10 UTC ---
On Tue, 9 Apr 2013, xanclic at gmail dot com wrote:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
>
> --- Comment #5 from Max Reitz 2013-04-09 13:02:19
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #5 from Max Reitz 2013-04-09 13:02:19
UTC ---
(In reply to comment #3)
> Just add -fno-tree-loop-distribute-patterns to the already long list of
> options
> you need for compilation of certain routines in your C library.
Th
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Co
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
--- Comment #2 from Mikael Pettersson 2013-04-09
09:59:20 UTC ---
Started with Richard Biener's http://gcc.gnu.org/r188261 aka PR53081 fix, which
added or improved memcpy recognition. I'm guess the new code fails to check
for whatever opt
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888
Mikael Pettersson changed:
What|Removed |Added
CC||mikpe at it dot uu.se
--- C
51 matches
Mail list logo
