Re: Solaris issues

Hi Paul, >> In Solaris 11.4, there were some changes here for better GNU (bug) >> compatibility, so there's only a single .rodata section here. >> However, >> there's nothing wrong with how Solaris ld behaved before: I'd claim >> this >> is a scalability bug in valgrind: ELF objects can have very

Re: Solaris issues

- Original Message - > Hi Paul, [snip - lots of .rodata sections] > > those sections are in libstdc++.so. They can be found in the input > objects used to created libstdc++.so on Linux and Solaris alike, due > to > the use of -fdata-sections (via SECTION_FLAGS) in libstdc++. > > Howev

Re: Solaris issues

Hi Paul, > I was only talking about adding support to aligned new/delete on Valgrind > (here is the bugzilla entry I created if you are interested > https://bugs.kde.org/show_bug.cgi?id=388787 > ) > > On Solaris (I’m using 11.3) Valgrind is having probl

Re: Solaris issues

- Original Message - > Hi Paul, > [Build issue on Solaris] > > this is PR target/85994. For the moment, you can just touch compare > and > resume the build. Trivial patch forthcoming... Hi Rainer This worked a treat, thanks. A+ Paul

Re: Solaris issues

> On 4 Jun 2018, at 16:50, Rainer Orth wrote: > > Hi Jonathan, > >> On 2 June 2018 at 11:29, Paul Floyd wrote: >>> Secondly I’ve been doing some work on adding support for C++14 and C++17 >>> sized/aligned new and delete operators. >> >> Aren't they already supported? I thought Solaris had

Re: Solaris issues

Hi Jonathan, > On 2 June 2018 at 11:29, Paul Floyd wrote: >> Secondly I’ve been doing some work on adding support for C++14 and C++17 >> sized/aligned new and delete operators. > > Aren't they already supported? I thought Solaris had aligned_alloc > and/or posix_memalign? posix_memalign had alre

Re: Solaris issues

Hi Paul, > I’ve been having 2 issues with GCC head on Solaris. Firstly. The build is > currently broken > > gmake[3]: Leaving directory `/export/home/paulf/scratch/gcc/build' > Comparing stages 2 and 3 > warning: gcc/cc1obj-checksum.o differs > Bootstrap comparison failure! > i386-pc-solaris2.11/

Re: Solaris issues

Hi That should be 'adding to valgrind' which I mentioned in the following paragraph. A+ Paul Original message From: Jonathan Wakely Date:2018/06/03 23:34 (GMT+01:00) To: Paul Floyd Cc: gcc@gcc.gnu.org Subject: Re: Solaris issues On 2 June 2018 at 1

Re: Solaris issues

On 2 June 2018 at 11:29, Paul Floyd wrote: > Secondly I’ve been doing some work on adding support for C++14 and C++17 > sized/aligned new and delete operators. Aren't they already supported? I thought Solaris had aligned_alloc and/or posix_memalign?

Solaris issues

Hi I’ve been having 2 issues with GCC head on Solaris. Firstly. The build is currently broken gmake[3]: Leaving directory `/export/home/paulf/scratch/gcc/build' Comparing stages 2 and 3 warning: gcc/cc1obj-checksum.o differs Bootstrap comparison failure! i386-pc-solaris2.11/amd64/libgcc/avx_resm