On Fri, Feb 28, 2025 at 13:54:45 -0500, Paul Smith wrote:
> On Fri, 2025-02-28 at 19:26 +0100, Ben Boeckel via Gcc wrote:
> > > In POSIX make, including GNU Make, if a command doesn't modify the
> > > modification time of the target then that target is not considered
> > > updated, and other target
On Fri, 2025-02-28 at 19:26 +0100, Ben Boeckel via Gcc wrote:
> > In POSIX make, including GNU Make, if a command doesn't modify the
> > modification time of the target then that target is not considered
> > updated, and other targets which list it as a prerequisite are not
> > invoked:
>
> Hmm. M
> Am 28.02.2025 um 20:02 schrieb Martin Uecker :
>
> Am Freitag, dem 28.02.2025 um 21:39 +0300 schrieb Alexander Monakov:
>>> On Fri, 28 Feb 2025, Martin Uecker via Gcc wrote:
>>>
>>>
>>> I have one follow-up question: What is the reason
>>> that we have stronger semantics for stores by def
I have one follow-up question: What is the reason
that we have stronger semantics for stores by default (i.e.
when not using -fallow-store-data-races) than for reads
given that the standard would allow more freedom.
Only that for reads this is more difficult to have?
Or other specific reasons w
On Fri, Feb 28, 2025 at 07:59:00 -0800, NightStrike via Gcc wrote:
> Could your approach simultaneously be used to have better dependency
> information for Fortran modules? I feel like there’s at least some overlap
> there.
P1689 is also intended to be suitable for Fortran (CMake uses it for its
F
Hi Joseph, Jakub,
On Thu, Feb 27, 2025 at 09:51:35PM +0100, Jakub Jelinek wrote:
> On Thu, Feb 27, 2025 at 08:44:25PM +, Joseph Myers via Gcc wrote:
> > On Thu, 27 Feb 2025, Alejandro Colomar via Gcc wrote:
> >
> > > Can you please confirm if we should add a version of this operator that
> >
Basile Starynkevitch writes:
> Hello Bright Andoh,
>
>>
>> My name is Bright Andoh, and I’m a Computer Engineering student at the
>> University of Alabama. I’m wrapping up my freshman year and have
>> experience working with Rust and C. Last fall, I collaborated on some
>> Rust projects with a f
On Fri, 2025-02-28 at 12:54 +0100, Basile Starynkevitch wrote:
> Hello Bright Andoh,
>
> >
> > My name is Bright Andoh, and I’m a Computer Engineering student at the
> > University of Alabama. I’m wrapping up my freshman year and have
> > experience working with Rust and C. Last fall, I collabora
On Fri, 28 Feb 2025, Martin Uecker via Gcc wrote:
>
> I have one follow-up question: What is the reason
> that we have stronger semantics for stores by default (i.e.
> when not using -fallow-store-data-races) than for reads
> given that the standard would allow more freedom.
Why would it? On
On Thu, Feb 27, 2025 at 21:39 vspefs via Gcc wrote:
> Current `-Mmodules` output is based on [P1602R0](wg21.link/p1602r0), which
> speaks about a set of Makefile rules that can handle modules, with the
> help of
> module mappers and a modified GNU Make.
>
> The proposal came out in 2019, and the
On Fri, 2025-02-28 at 18:05 +0100, Ben Boeckel via Gcc wrote:
> Note that one thing that is missing is ninja's `restat = 1` feature.
> This "restats" the output for the associated rule (probably spelled
> `.RESTAT: output` in Make) and skips running dependent rules if the
> output has not updated t
On Fri, 2025-02-28 at 13:07 -0500, Paul Smith via Gcc wrote:
> ~$ touch three; make -f /tmp/x3.mk MKTWO=echo
Sorry this should be just "make MKTWO=echo"; my typo.
Am Freitag, dem 28.02.2025 um 08:18 +0100 schrieb Richard Biener via Gcc:
> On Fri, Feb 28, 2025 at 8:01 AM Martin Uecker wrote:
> >
> >
> > Hi all,
> >
> > one area where the Linux kernel people are unhappy with C's
> > memory model is where they now have to use the READ_ONCE,
> > WRITE_ONCE m
Hi,
On Sat, Mar 01 2025, 岡田隆太郎 via Gcc wrote:
> Hello,
>
> My name is Ryutaro Okada. I am interested in participating in Google Summer
> of Code 2024 with the GCC organization.
Presumably 2025? ;-)
> I am particularly fascinated by the
> project "Rewrite Rust lints to operate on our frontend's H
On Fri, Feb 28, 2025 at 13:07:04 -0500, Paul Smith wrote:
> On Fri, 2025-02-28 at 18:05 +0100, Ben Boeckel via Gcc wrote:
> > Note that one thing that is missing is ninja's `restat = 1` feature.
> > This "restats" the output for the associated rule (probably spelled
> > `.RESTAT: output` in Make) a
Hello,
On Thu, Feb 27 2025, Bright Andoh via Gcc wrote:
> Hello GCC Rust Team,
>
> My name is Bright Andoh, and I’m a Computer Engineering student at the
> University of Alabama. I’m wrapping up my freshman year and have
> experience working with Rust and C. Last fall, I collaborated on some
> Rus
Hello Bright Andoh,
>
> My name is Bright Andoh, and I’m a Computer Engineering student at the
> University of Alabama. I’m wrapping up my freshman year and have
> experience working with Rust and C. Last fall, I collaborated on some
> Rust projects with a friend, and I’m eager to deepen my under
On Fri, 2025-02-28 at 12:00 +, Sam James wrote:
> Basile Starynkevitch writes:
>
> > Hello Bright Andoh,
> >
> > >
> > > My name is Bright Andoh, and I’m a Computer Engineering student at the
> > > University of Alabama. I’m wrapping up my freshman year and have
> > > experience working wit
Hello,
My name is Ryutaro Okada. I am interested in participating in Google Summer
of Code 2024 with the GCC organization. I am particularly fascinated by the
project "Rewrite Rust lints to operate on our frontend's HIR instead of
using GCC's existing infrastructure."
I have prior experience in c
Am Freitag, dem 28.02.2025 um 20:21 +0100 schrieb Richard Biener:
>
> > Am 28.02.2025 um 20:02 schrieb Martin Uecker :
> >
> > Am Freitag, dem 28.02.2025 um 21:39 +0300 schrieb Alexander Monakov:
> > > > On Fri, 28 Feb 2025, Martin Uecker via Gcc wrote:
> > > >
> > > >
> > > > I have one follo
20 matches
Mail list logo
