NightStrike wrote:
On Sat, Dec 17, 2022 at 10:44 PM Jacob Bachmeyer wrote:
[...]
This is either a testsuite problem or an environment problem. The GNU
Fortran I/O module certainly has interesting behavior here. Try setting
TERM=dumb in the environment while running the testsuite. If that
Hello,
I would like to fix the -fprofile-update=atomic implementation so that
it works on all targets. Currently, it works only on targets with 64-bit
atomic operations in hardware (and some special cases). I tried to fix
it like this:
https://gcc.gnu.org/pipermail/gcc-patches/2022-December/
On 12/17/22 20:35, Martin Uecker wrote:
Hi all,
what is the process for adding a new UBsan handler?
Hello.
Yes, we sync the run-time library from LLVM project. So a new sanitizer
should go there first.
We have the source in the GCC tree, but I guess this
should go via LLVM?
And the com
Am Montag, dem 19.12.2022 um 09:44 +0100 schrieb Martin Liška:
> On 12/17/22 20:35, Martin Uecker wrote:
> >
> >
> > Hi all,
> >
> > what is the process for adding a new UBsan handler?
>
> Hello.
>
> Yes, we sync the run-time library from LLVM project. So a new
> sanitizer
> should go there fi
Hi,
> -Original Message-
> From: dejagnu-bounces+torbjorn.svensson=st@gnu.org bounces+torbjorn.svensson=st@gnu.org> On Behalf Of Jacob Bachmeyer
> Sent: den 19 december 2022 05:29
> To: NightStrike
> Cc: Thomas Koenig ; fort...@gcc.gnu.org; gcc
> mailing list ; deja...@gnu.org
>
On Mon, Dec 19, 2022 at 5:43 AM Torbjorn SVENSSON
wrote:
> I'm not sure if this helps anyone, but I experienced something similar with
> Cygwin a while back.
> What I had to do in order to have expect working when testing GCC on Windows
> 10 was to defined the "CYGWIN" environment variable to "d
On Thu, 15 Dec 2022 at 16:54, U.Mutlu wrote:
>
> On this page all ISO C++ standards versions of gcc/g++ are listed, except
> C++03:
> https://gcc.gnu.org/projects/cxx-status.html
>
> This looks much like an error/omission b/c g++ has the options -std=c++03 and
> -std=gnu++03
Hi,
If you're going
On Sun, Dec 18, 2022 at 11:29 PM Jacob Bachmeyer wrote:
>
> NightStrike wrote:
> > On Sat, Dec 17, 2022 at 10:44 PM Jacob Bachmeyer wrote:
> >
> >> [...]
> >> This is either a testsuite problem or an environment problem. The GNU
> >> Fortran I/O module certainly has interesting behavior here. T
On Mon, 19 Dec 2022 at 11:19, Sebastian Huber wrote:
>
> Hello,
>
> I would like to fix the -fprofile-update=atomic implementation so that
> it works on all targets. Currently, it works only on targets with 64-bit
> atomic operations in hardware (and some special cases). I tried to fix
> it like th
On 19/12/2022 13:41, Jonathan Wakely wrote:
3. Use gthr as the default implementation of libatomic.
I have no objection to doing this, but I don't see why you need to
touch libstdc++ to do it. Just make libatomic create its own copy of
gthr.h (if a fallback gthreads-based implementation is actua
在 2022/12/19 20:45, Sebastian Huber 写道:
On 19/12/2022 13:41, Jonathan Wakely wrote:
3. Use gthr as the default implementation of libatomic.
I have no objection to doing this, but I don't see why you need to
touch libstdc++ to do it. Just make libatomic create its own copy of
gthr.h (if a fallba
On 12/19/22 10:25, Martin Uecker wrote:
Am Montag, dem 19.12.2022 um 09:44 +0100 schrieb Martin Liška:
On 12/17/22 20:35, Martin Uecker wrote:
Hi all,
what is the process for adding a new UBsan handler?
Hello.
Yes, we sync the run-time library from LLVM project. So a new
sanitizer
should
Am Montag, dem 19.12.2022 um 15:22 +0100 schrieb Martin Liška:
> On 12/19/22 10:25, Martin Uecker wrote:
> > Am Montag, dem 19.12.2022 um 09:44 +0100 schrieb Martin Liška:
> > > On 12/17/22 20:35, Martin Uecker wrote:
> > > >
> > > >
> > > > Hi all,
> > > >
> > > > what is the process for adding
NightStrike wrote:
On Sun, Dec 18, 2022 at 11:29 PM Jacob Bachmeyer wrote:
NightStrike wrote:
On Sat, Dec 17, 2022 at 10:44 PM Jacob Bachmeyer wrote:
[...]
This is either a testsuite problem or an environment problem. The GNU
Fortran I/O module certainly has interesting beha
On Fri, 3 Sept 2021 at 20:12, Ulrich Weigand
wrote:
> "Paul Edwards" wrote on 03.09.2021 13:35:10:
> > > Specifically, if you try to run AMODE64 with Pmode equals
> > > SImode, the compiler will not be aware that the hardware
> > > uses the high 32 bits of base and index registers, and
> > >
15 matches
Mail list logo