The GCC 5 branch is now frozen for creating a first release candidate
for GCC 5.3. All changes from now on require release manager approval.
Thanks,
Richard.
The first release candidate for GCC 5.3 is available from
ftp://gcc.gnu.org/pub/gcc/snapshots/5.3.0-RC-20151130
and shortly its mirrors. It has been generated from SVN revision 231055.
I have sofar bootstrapped the release candidate on x86_64-suse-linux-gnu.
Please test the release
On 11/29/2015 11:53 PM, David Wohlferd wrote:
>
> Trying to guess what people might have been expecting is a losing game.
We have to do it all the time.
> There is a way for people to be clear about what they want to clobber,
> and that's to use extended asm. The way to clear up the ambiguit
> On Nov 29, 2015, at 6:53 PM, David Wohlferd wrote:
>
>
>
> On 11/28/2015 10:30 AM, paul_kon...@dell.com wrote:
>>> On Nov 28, 2015, at 2:02 AM, Bernd Edlinger
>>> wrote:
>>>
>>> ...
>>> Well, I start to think that Jeff is right, and we should treat a asm ("")
>>> as if it
>>> were asm vo
On 11/28/2015 08:42 AM, Ulrich Drepper wrote:
After the Solaris vtv port was added my build of the x86 gcc with x32
support fails. The build is special since the kernel doesn't have x32
support and I cannot directly run x32 binaries (they are run in a kvm
kernel). This is used to work well by c
On Mon, Nov 30, 2015 at 6:57 PM, Jeff Law wrote:
> What part of this requires bits to run? I see AC_COMPILE_IFELSE, but not
> anything which obviously requires running the resulting code.
Without AC_USE_SYSTEM_EXTENSIONS one gets:
configure.ac:111: warning: AC_COMPILE_IFELSE was called before
A
On 11/30/2015 05:25 PM, Ulrich Drepper wrote:
On Mon, Nov 30, 2015 at 6:57 PM, Jeff Law wrote:
What part of this requires bits to run? I see AC_COMPILE_IFELSE, but not
anything which obviously requires running the resulting code.
Without AC_USE_SYSTEM_EXTENSIONS one gets:
configure.ac:111:
dir=/usr/share/man --infodir=/usr/share/info
--enable-vtable-verify
configure:2863: checking for C compiler default output file name
configure:2885:
/home/drepper/local/gcc-builds/test-20151130/./gcc/xgcc
-B/home/drepper/local/gcc-builds/test-20151130/./gcc/ -B/us
r/x86_64-redhat-linux/bin/ -B/usr/x86_6
On 01.12.2015 03:58, Ulrich Drepper wrote:
On Mon, Nov 30, 2015 at 9:14 PM, Jeff Law wrote:
Right, but isn't AC_COMPILE_IFELSE a compile test, not a run test?
The problem macro is _AC_COMPILER_EXEEXT_WORKS. The message is at the end.
This macro *should* work for cross-compiling but somehow
