On Tue, Apr 12, 2022 at 1:53 AM Steve Kargl via Gcc wrote:
>
> If I configure gcc with the following
>
> ../gccx/configure --prefix=$HOME/work/x --enable-languages=c,c++,fortran \
> --enable-bootstrap --disable-nls --enable-checking --disable-multilib \
> --disable-libsanitizer --disable-lto.
On Tue, Apr 12, 2022 at 9:07 AM Richard Biener
wrote:
>
> On Tue, Apr 12, 2022 at 1:53 AM Steve Kargl via Gcc wrote:
> >
> > If I configure gcc with the following
> >
> > ../gccx/configure --prefix=$HOME/work/x --enable-languages=c,c++,fortran \
> > --enable-bootstrap --disable-nls --enable-che
Hi Nick,
On 4/8/22 14:36, Nick Clifton wrote:
Hi Luis,
There is a CVE [1] for zlib < 1.2.12 (released march 27th).
GCC currently uses zlib 1.2.11, and binutils-gdb imports the zlib
directory from GCC. The recommendation is to get it updated to 1.2.12,
which contains the proper fix [2].
I
On Apr 11 2022, Steve Kargl via Gcc wrote:
> Should the testsuite recognize that gcc is built without LTO support?
Yes, we have check_effective_target_lto for that.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for som
Hi,
>
>
> > On 08-Apr-2022, at 6:32 PM, Jan Hubicka wrote:
> >
> > Ankur,
> >> I was browsing the list of submitted GSoC projects this year and the
> >> project regarding bypassing assembler when generating LTO object files
> >> caught my eye.
> > I apologize for late reply. I would be very ha
On Tue, Apr 12, 2022 at 11:20 AM Jan Hubicka via Gcc wrote:
>
> Hi,
> >
> >
> > > On 08-Apr-2022, at 6:32 PM, Jan Hubicka wrote:
> > >
> > > Ankur,
> > >> I was browsing the list of submitted GSoC projects this year and the
> > >> project regarding bypassing assembler when generating LTO object f
On 4/12/22 11:58, Richard Biener wrote:
On Tue, Apr 12, 2022 at 11:20 AM Jan Hubicka via Gcc wrote:
Hi,
On 08-Apr-2022, at 6:32 PM, Jan Hubicka wrote:
Ankur,
I was browsing the list of submitted GSoC projects this year and the
project regarding bypassing assembler when generating LTO ob
> On 12 Apr 2022, at 13:31, Martin Liška wrote:
>
> On 4/12/22 11:58, Richard Biener wrote:
>> On Tue, Apr 12, 2022 at 11:20 AM Jan Hubicka via Gcc wrote:
>>>
>>> Hi,
> On 08-Apr-2022, at 6:32 PM, Jan Hubicka wrote:
>
> Ankur,
>> I was browsing the list of submi
On Tue, Apr 12, 2022 at 2:53 PM Iain Sandoe wrote:
>
>
>
> > On 12 Apr 2022, at 13:31, Martin Liška wrote:
> >
> > On 4/12/22 11:58, Richard Biener wrote:
> >> On Tue, Apr 12, 2022 at 11:20 AM Jan Hubicka via Gcc
> >> wrote:
> >>>
> >>> Hi,
>
>
> > On 08-Apr-2022, at 6:32 PM, Jan
Hi Luis,
There is a CVE [1] for zlib < 1.2.12 (released march 27th).
GCC currently uses zlib 1.2.11, and binutils-gdb imports the zlib directory
from GCC. The recommendation is to get it updated to 1.2.12, which contains the
proper fix [2].
Right - I have now updated the binutils-gdb mainl
On Tue, Apr 12, 2022 at 09:26:58AM +0200, Richard Biener wrote:
> On Tue, Apr 12, 2022 at 9:07 AM Richard Biener
> wrote:
> >
> > On Tue, Apr 12, 2022 at 1:53 AM Steve Kargl via Gcc wrote:
> > >
> > > If I configure gcc with the following
> > >
> > > ../gccx/configure --prefix=$HOME/work/x --enab
On Tue, 12 Apr 2022 at 18:32, Steve Kargl wrote:
> Well, I determined what the problem is. On FreeBSD,
> GNU make is gmake. make(1) on FreeBSD is BSD make.
>
> % gmake -j7 check-c
>
> Does not pass down the name of the invoking command
> to sub-make jobs.
That suggests some makefile is using 'ma
On Tue, Apr 12, 2022 at 06:42:20PM +0100, Jonathan Wakely wrote:
> On Tue, 12 Apr 2022 at 18:32, Steve Kargl wrote:
> > Well, I determined what the problem is. On FreeBSD,
> > GNU make is gmake. make(1) on FreeBSD is BSD make.
> >
> > % gmake -j7 check-c
> >
> > Does not pass down the name of the
13 matches
Mail list logo
