f【袋-【开---税】--票】-电话:136-4072-5689

2018-05-07 Thread ollnxfkj
gd【袋-【开---税】--票】-电话:136-4072-5689

fminnm/fmaxnm generation in aarch64

2018-05-07 Thread Indu Bhagat
[Trying to get some feedback. I earlier posted on gcc-help a week ago] In tree.def - /* Minimum and maximum values. When used with floating point, if both operands are zeros, or if either operand is NaN, then it is unspecified which of the two operands is returned as the result. */ DEFTRE

Re: Successful bootsrap of gcc 8.1.0 on x86_64-w64-mingw32

2018-05-07 Thread Jonathan Wakely
On 6 May 2018 at 16:44, Rainer Emrich wrote: > Bootstrap is done with msys2 on Windows 7. For the testsuite results see > https://gcc.gnu.org/ml/gcc-testresults/2018-05/msg00583.html Thanks for this. Would you be able to send me the $objdir/$target/libstdc++-v3/testsuite/libstdc++.log file?

Re: GCC Compiler Optimization ignores or mistreats MFENCE memory barrier related instruction

2018-05-07 Thread Jakub Jelinek
On Mon, May 07, 2018 at 01:58:48PM +0530, Umesh Kalappa wrote: > CCed Jakub, > > Agree that float division don't touch memory ,but fdiv result (stack > > register ) is stored back to a memory i.e fResult . That doesn't really matter. It is stored to a stack spill slot, something that doesn't h

Re: GCC Compiler Optimization ignores or mistreats MFENCE memory barrier related instruction

2018-05-07 Thread Umesh Kalappa
CCed Jakub, > Hi Alex, > Agree that float division don't touch memory ,but fdiv result (stack > register ) is stored back to a memory i.e fResult . > > So compiler barrier in the inline asm i.e ::memory should prevent the > shrinkage of instructions like "fstps fResult(%rip)"behind the