https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113078
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113076
Richard Biener changed:
What|Removed |Added
Target||riscv
--- Comment #1 from Richard Bien
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113073
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113070
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113082
--- Comment #3 from rguenther at suse dot de ---
On Tue, 19 Dec 2023, fw at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113082
>
> --- Comment #2 from Florian Weimer ---
> (In reply to Richard Biener from comment #1)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113045
--- Comment #15 from David Binderman ---
(In reply to Jonathan Wakely from comment #12)
> Because otherwise I'm going to get blamed for every bug older than
> 2022-11-01!
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111270#c1
My apologies for
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=113045
--- Comment #14 from David Binderman ---
(In reply to Andrew Pinski from comment #9)
> Does it work correctly without valgrind?
Yes. No one has yet attempted to reproduce my results.
vld1q_u8 is a 128 bit ARM hardware instruction.
I assume tha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110651
Francois-Xavier Coudert changed:
What|Removed |Added
Keywords||patch
Status|UNCO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113082
--- Comment #2 from Florian Weimer ---
(In reply to Richard Biener from comment #1)
> Joseph - I wonder if the standard folks can be convinced to amend most
> library function documentation as to not altering 'errno' (like memcpy,
> strlen, etc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113082
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2023-12-19
Status|UNCONFIR
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=113082
Bug ID: 113082
Summary: builtin transforms do not honor errno
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-e
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
101 - 114 of 114 matches
Mail list logo