Re: Optimization breaks inline asm code w/ptrs

2017-08-13 Thread David Wohlferd
On 8/12/2017 10:14 PM, Andrew Pinski wrote: On Sat, Aug 12, 2017 at 10:08 PM, Andrew Pinski wrote: On Sat, Aug 12, 2017 at 9:21 PM, David Wohlferd wrote: Environment: gcc 6.1 compiling for 64bit i386 optimizations: -O2 Consider this simple bit of code (from https://stackoverflow.com/a/456560

Re: Optimization breaks inline asm code w/ptrs

2017-08-13 Thread Alan Modra
On Sun, Aug 13, 2017 at 03:35:15AM -0700, David Wohlferd wrote: > Using "m"(*pStr) as an (unused) input parameter has no effect. Use "m" (*(const void *)pStr) and ignore the warning, or use "m" (*(const struct {char a; char x[];} *) pStr). The issue is one of letting gcc know what memory is acces

Behaviour of __forced_unwind with noexcept

2017-08-13 Thread Ron
Hi, I'm looking for some clarification of how the __forced_unwind thread cancellation exceptions intersect with noexcept. I've long been a big fan of the __forced_unwind idiom, but now that C++14 is the default since GCC 6.1, and many methods including destructors are implicitly noexcept, using

gcc-8-20170813 is now available

2017-08-13 Thread gccadmin
Snapshot gcc-8-20170813 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/8-20170813/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 8 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision

[i386, x32] Trouble bootstrapping x86_64-pc-linux-gnux32

2017-08-13 Thread Daniel Santos
I've setup an x32 test environment using Gentoo in hopes of being able to both compile and run x32 tests, but I'm having problems getting a successful bootstrap. I'm guessing this is due to something currently broken with x32, but I want to make sure it's not something I'm doing wrong, and if it i

Re: [i386, x32] Trouble bootstrapping x86_64-pc-linux-gnux32

2017-08-13 Thread H.J. Lu
On Sun, Aug 13, 2017 at 3:52 PM, Daniel Santos wrote: > I've setup an x32 test environment using Gentoo in hopes of being able > to both compile and run x32 tests, but I'm having problems getting a > successful bootstrap. I'm guessing this is due to something currently > broken with x32, but I wa

Re: gcc behavior on memory exhaustion (bug 81818)

2017-08-13 Thread Andrew Roberts
I've updated this bug [Bug 81818 - aarch64 uses 2-3x memory and 2x time of arm at -Os, -O2, -O3] with more info. It looks to be that on ARM systems with limited RAM optimizations are being skipped, but not on AARCH64. Is there a way I can check this is true? I checked all the optimizations e