Re: build system: gcc_cv_libc_provides_ssp and NATIVE_SYSTEM_HEADER_DIR
Thomas Schwinge, le Fri 10 Oct 2008 10:37:50 +0200, a écrit : > Ideally, IMO, this test (for stack-smashing-protection support in glibc) > should not be done by grepping through SYSROOT's features.h, but instead > by using the CPP for doing that. The problem is that CPP has not yet > been bulit at the place where the test is currently been done (in GCC's > configure). Err, ok but can't we use the host's cpp? That one is supposed to be able to parse features.h Samuel
Re: Inquiry about GCC Summer Of Code project idea.
Ian Lance Taylor, le Mon 25 Mar 2013 08:22:15 -0700, a écrit : > > - What would be a skill level estimate for someone wishing to try this > > project in an attempt to get his feet wet in compiler engineering? > > Unfortunately it's hard for me to judge. The most important skill > would be the ability to dig into some large code bases and understand > how to change them. Agreed. I don't think there would be much about compiler engineering actually, but rather about runtime and system calls. Samuel
Re: setcontext et al. functions (was: Inquiry about GCC Summer Of Code project idea.)
Thomas Schwinge, le Tue 11 Jun 2013 10:27:09 +0200, a écrit : > Anyway, Samuel, would you please > put the current »tg patch t/context_functions« as a new patch into the > Debian glibc package? Yep, it is done, waiting for next upload. Samuel
Re: Tool chain configuration: GNU/* sharing stuff with GNU/Linux
Thomas Schwinge, le Sun 11 Nov 2007 15:58:08 +0100, a écrit : > To state this intended similarity clearly, one could rename, e.g., > `config/linux.h' to `config/gnu-shared.h' and then have a new (nearly > empty) file `config/linux.h' additionally to the existing `config/gnu.h', > `config/kfreebsd-gnu.h', etc. to do the remaining few customizations. That'd make things much more clear (and fix the OPTION_GLIBC etc. bugs btw). Samuel
Re: Failures building glibc with mainline GCC
Joseph Myers, le mar. 03 août 2021 17:21:59 +, a ecrit: > On Tue, 3 Aug 2021, Martin Sebor via Gcc wrote: > > > Yes, we know about that one. What I'm asking for is the translation > > units with the other warnings you showed with the latest GCC (including > > the threader patches) on the other targets (including i686 and power). > > I don't have an easy way to create them using my setup. > > I've attached (all gzipped) hurdselect.i (i686-gnu, -O2 -Wall -Werror > -Wno-parentheses): > > hurdselect.c: In function '_hurd_select': > hurdselect.c:555:7: error: 'ss' may be used uninitialized in this function > [-Werror=maybe-uninitialized] > hurdselect.c:70:25: note: 'ss' was declared here That's a spurious warning, but I have pushed a trivial workaround. Samuel
