https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100693
Will Schmidt changed:
What|Removed |Added
CC||willschm at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104643
Will Schmidt changed:
What|Removed |Added
CC||bergner at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103686
--- Comment #11 from Will Schmidt ---
(In reply to Bill Schmidt from comment #10)
> It turns out not to be undocumented -- but I'd like to remove it anyway.
> Any objections?
Realistically I believe I was the only user of that feature, was to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103051
Will Schmidt changed:
What|Removed |Added
CC||segher at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101882
Bug ID: 101882
Summary: modulus with input and output set to a hard register
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98692
--- Comment #14 from Will Schmidt ---
Using gdb/vgdb to view the valgrind shadow register values, it looks like
the uninitialized values are being loaded in via the
_restgpr0_25 call being made at the end of isVariable().
Dump of assembler cod
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98692
--- Comment #11 from Will Schmidt ---
(In reply to Mark Wielaard from comment #10)
> (In reply to Will Schmidt from comment #9)
> > (In reply to Segher Boessenkool from comment #5)
> > > Have you tried a new valgrind?
> > >
> > > Either this is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98692
Will Schmidt changed:
What|Removed |Added
CC||willschm at gcc dot gnu.org
--- Comment #
