https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101779
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101779
Nick Clifton changed:
What|Removed |Added
CC||nickc at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101779
--- Comment #3 from Eli Zaretskii ---
(In reply to Jonathan Wakely from comment #2)
> Binutils 2.37 has the fix for GCC PR 99935 included, so I suggest adding a
> comment to that bug instead.
I see that you already reported the issue there (tha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101779
--- Comment #2 from Jonathan Wakely ---
Binutils 2.37 has the fix for GCC PR 99935 included, so I suggest adding a
comment to that bug instead.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101779
Richard Biener changed:
What|Removed |Added
Target||mingw32
Status|UNCONFIRMED
> From: Andrew Pinski
> Date: Wed, 4 Aug 2021 11:57:47 -0700
> Cc: Jonathan Wakely , GCC Bugs ,
> Andreas Schwab
>
> > > https://gcc.gnu.org/bugs/ instead.
> >
> > Which points to GCC Bugzilla, which doesn't have a "libiberty"
> > component. So I suggest to add such a component on the Bu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101779
Bug ID: 101779
Summary: Compilation of rust-demangle.c fails on MinGW
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component
On Wed, Aug 4, 2021 at 8:46 AM Eli Zaretskii via Gcc-bugs
wrote:
>
> > Date: Wed, 4 Aug 2021 15:41:30 +0100
> > From: Jonathan Wakely
> > Cc: gcc-bugs@gcc.gnu.org, e...@gnu.org
> >
> > > The libiberty README says to report bugs to gcc-bugs@gcc.gnu.org.
> >
> > Well that needs to be fixed. It shou
> Date: Wed, 4 Aug 2021 15:41:30 +0100
> From: Jonathan Wakely
> Cc: gcc-bugs@gcc.gnu.org, e...@gnu.org
>
> > The libiberty README says to report bugs to gcc-bugs@gcc.gnu.org.
>
> Well that needs to be fixed. It should point to
> https://gcc.gnu.org/bugs/ instead.
Which points to GCC Bugzilla,
> The libiberty README says to report bugs to gcc-bugs@gcc.gnu.org.
Well that needs to be fixed. It should point to
https://gcc.gnu.org/bugs/ instead.
> From: Andreas Schwab
> Cc: Richard Sandiford , Eli Zaretskii
>
> Date: Wed, 04 Aug 2021 15:35:04 +0200
>
> On Aug 04 2021, Eli Zaretskii via Gcc-bugs wrote:
>
> > I'd love to, but please tell me where. I couldn't find any
> > information about reporting libiberty bugs, sorry if I missed
>
> Date: Wed, 4 Aug 2021 14:03:21 +0100
> From: Jonathan Wakely
> Cc: gcc-bugs@gcc.gnu.org
>
> In GCC's bugzilla.
That's what I tried originally, but there's no libiberty there among
the various "components". So I decided the GCC Bugzilla was not the
right place. If it is the right place, pleas
On Aug 04 2021, Eli Zaretskii via Gcc-bugs wrote:
> I'd love to, but please tell me where. I couldn't find any
> information about reporting libiberty bugs, sorry if I missed
> something obvious.
The libiberty README says to report bugs to gcc-bugs@gcc.gnu.org.
Andreas.
--
Andreas Schwab, sch
In GCC's bugzilla. You could also report it to the sourceware.org
bugzilla for binutils, but I think GCC is the upstream for libiberty.
> From: Richard Sandiford
> Cc: Eli Zaretskii
> Date: Wed, 04 Aug 2021 13:04:24 +0100
>
> Eli Zaretskii via Gcc-bugs writes:
> > The version of rust-demangle.c included with Binutils 2.37 doesn't
> > compile with MinGW:
> >
> > mingw32-gcc -c -DHAVE_CONFIG_H -O2 -gdwarf-4 -g3 -I.
> >
Hi,
Eli Zaretskii via Gcc-bugs writes:
> The version of rust-demangle.c included with Binutils 2.37 doesn't
> compile with MinGW:
>
> mingw32-gcc -c -DHAVE_CONFIG_H -O2 -gdwarf-4 -g3 -I.
> -I../../binutils-2.37/libiberty/../include -W -Wall -Wwrite-strings
> -Wc++-compat -Wstrict-pr
The version of rust-demangle.c included with Binutils 2.37 doesn't
compile with MinGW:
mingw32-gcc -c -DHAVE_CONFIG_H -O2 -gdwarf-4 -g3 -I.
-I../../binutils-2.37/libiberty/../include -W -Wall -Wwrite-strings
-Wc++-compat -Wstrict-prototypes -Wshadow=local -pedantic -D_GNU_SOURCE
17 matches
Mail list logo
