On Fri, 27 Nov 2015, Joseph Myers wrote:
> > I find it highly unlikely though that the writers will (be able to) chase
> > individual targets and any obscure hardware-dependent options the targets
> > may provide. And we cannot expect people compiling software to be
>
> What that says to me i
On 01/06/2016 07:46 PM, Toon Moene wrote:
[ This is relevant for our code, because just the switch to *actual*
single precision exp/log/sin/cos implementations in glibc's libm
resulted in a decrease of the running time of our weather forecasting
code by 25 % (this was in glibc 2.16, IIR
Snapshot gcc-4.9-20160106 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.9-20160106/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.9 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
On 4 January 2016 at 09:32, Florian Weimer wrote:
> On 12/31/2015 01:31 PM, Jonathan Wakely wrote:
>> On 31 December 2015 at 11:37, Marc Glisse wrote:
>>> That's what I called "bug" in my message (there are a few bugzilla PRs for
>>> this). It would probably work on Solaris.
>>
>> Yes, the case is
On 2 January 2016 at 11:42, Jonathan Wakely wrote:
> On 31 December 2015 at 18:49, James Dennett wrote:
>> On Thu, Dec 31, 2015 at 4:42 AM, Jonathan Wakely
>> wrote:
>>>
>>> On 31 December 2015 at 11:54, Dominik Vogt wrote:
>>> > Is there a requirement for a certain minimum Glibc version for
>>>
All,
I noticed, around half a year ago, that the incredible team around glibc
found the time to implement vector math (libm) routines.
Previously, free software adherents like me were dependent on vendor
libraries via the -mveclibabi={svml|acml} (on Intel/AMD) for instance.
However, the exa
On 01/06/2016 08:17 AM, Ian Lance Taylor wrote:
The bug report https://golang.org/issue/13662 describes a case in
which ivopts appears to be breaking garbage collection for the Go
compiler. There is an array allocated in memory, and there is a loop
over that array. The ivopts optimization is ta
The bug report https://golang.org/issue/13662 describes a case in
which ivopts appears to be breaking garbage collection for the Go
compiler. There is an array allocated in memory, and there is a loop
over that array. The ivopts optimization is taking the only pointer
to the array and subtracting
On Tue, Jan 05, 2016 at 05:43:47PM +, Alan Lawrence wrote:
> Can anyone give me any pointers on how to use the -mpaired option ("PowerPC
> 750CL paired-single instructions") ?
Configure your compiler with --target=powerpc-elf-paired, maybe add
--with-cpu=750 ?
> I'm trying to get it to use t
