Not seeing anyone doing the obvious one-up, so JFTR:
On Mon, 10 Jan 2022, David Malcolm via Gcc wrote:
> On Mon, 2022-01-10 at 17:13 +0100, FX wrote:
> > > FAIL: gcc.dg/analyzer/asm-x86-lp64-1.c
>
> The purpose of these asm tests is to verify that the analyzer doesn't
> get confused by various in
Snapshot gcc-11-20220115 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20220115/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
> On Jan 15, 2022, at 4:28 PM, Martin Sebor wrote:
>
> On 1/14/22 07:58, Paul Koning via Gcc wrote:
>>> On Jan 14, 2022, at 9:15 AM, Michael Matz via Gcc wrote:
>>>
...
>>> But right now that's equivalent to making it observable,
>>> because we don't have any other terms than observable
On 1/14/22 07:58, Paul Koning via Gcc wrote:
On Jan 14, 2022, at 9:15 AM, Michael Matz via Gcc wrote:
Hello,
On Thu, 13 Jan 2022, Martin Uecker wrote:
Handling all volatile accesses in the very same way would be
possible but quite some work I don't see much value in.
I see some value.
Am Samstag, den 15.01.2022, 16:33 + schrieb Jonathan Wakely:
> On Sat, 15 Jan 2022, 09:00 Martin Uecker, wrote:
>
> > Am Freitag, den 14.01.2022, 19:54 + schrieb Jonathan Wakely:
> > > On Fri, 14 Jan 2022, 14:17 Michael Matz via Gcc,
> > wrote:
> > > > Hello,
> > > >
> > > > On Thu, 13
On Sat, 15 Jan 2022, 09:00 Martin Uecker, wrote:
> Am Freitag, den 14.01.2022, 19:54 + schrieb Jonathan Wakely:
> > On Fri, 14 Jan 2022, 14:17 Michael Matz via Gcc,
> wrote:
> >
> > > Hello,
> > >
> > > On Thu, 13 Jan 2022, Martin Uecker wrote:
> > >
> > > > > > > Handling all volatile acce
Hi FX,
> On 15 Jan 2022, at 14:19, FX via Gcc wrote:
>
>> The purpose of these asm tests is to verify that the analyzer doesn't
>> get confused by various inline assembler directives used in the source
>> of the Linux kernel. So in theory they ought to work on any host, with
>> a gcc configured
Hi David,
> The purpose of these asm tests is to verify that the analyzer doesn't
> get confused by various inline assembler directives used in the source
> of the Linux kernel. So in theory they ought to work on any host, with
> a gcc configured for a suitable target.
>
> These tests are marked
On Sat, Jan 15, 2022 at 5:07 AM Purvak Baliyan via Gcc wrote:
>
> Respected Sir/Madam
>
> I am Purvak Baliyan, an Information Technology undergrad, I have entered my
> third year at DR. Akhilesh Das Gupta Institute of Technology &
> Management(ADGITM). I am new to open source contributions but i a
Respected Sir/Madam
I am Purvak Baliyan, an Information Technology undergrad, I have entered my
third year at DR. Akhilesh Das Gupta Institute of Technology &
Management(ADGITM). I am new to open source contributions but i am well
aware of C/C++, Data Structure and Algorithms, and HTML & CSS. I wo
Am Freitag, den 14.01.2022, 19:54 + schrieb Jonathan Wakely:
> On Fri, 14 Jan 2022, 14:17 Michael Matz via Gcc, wrote:
>
> > Hello,
> >
> > On Thu, 13 Jan 2022, Martin Uecker wrote:
> >
> > > > > > Handling all volatile accesses in the very same way would be
> > > > > > possible but quite
11 matches
Mail list logo
