Am Samstag, dem 27.07.2024 um 00:26 +0200 schrieb Alejandro Colomar:
> On Sat, Jul 27, 2024 at 12:03:20AM GMT, Martin Uecker wrote:
> > > Maybe if GNU C compilers (GCC and Clang) add it first as an extension,
> > > adding diagnostics, it would help.
> >
> > Both GCC and Clang already have such dia
Snapshot gcc-13-20240726 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20240726/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On Sat, Jul 27, 2024 at 12:03:20AM GMT, Martin Uecker wrote:
> > Maybe if GNU C compilers (GCC and Clang) add it first as an extension,
> > adding diagnostics, it would help.
>
> Both GCC and Clang already have such diagnostics and/or run-time checks:
>
> https://godbolt.org/z/MPnxqb9h7
Hi Marti
Am Freitag, dem 26.07.2024 um 23:49 +0200 schrieb Alejandro Colomar via Gcc:
> On Fri, Jul 26, 2024 at 09:22:42PM GMT, Joseph Myers wrote:
> > On Fri, 26 Jul 2024, Alejandro Colomar via Gcc wrote:
> >
> > > > See reflector message SC22WG14.18575, 17 Nov 2020 (the former convenor
> > > > replying
On Fri, Jul 26, 2024 at 09:22:42PM GMT, Joseph Myers wrote:
> On Fri, 26 Jul 2024, Alejandro Colomar via Gcc wrote:
>
> > > See reflector message SC22WG14.18575, 17 Nov 2020 (the former convenor
> > > replying when I asked about just that paper).
> >
> > Where can I find reflector messages?
>
>
On Fri, 26 Jul 2024, Alejandro Colomar via Gcc wrote:
> > See reflector message SC22WG14.18575, 17 Nov 2020 (the former convenor
> > replying when I asked about just that paper).
>
> Where can I find reflector messages?
https://www.open-std.org/jtc1/sc22/wg14/18575
> And another one to propose
Hi Joseph,
On Fri, Jul 26, 2024 at 08:30:33PM GMT, Joseph Myers wrote:
> On Fri, 26 Jul 2024, Alejandro Colomar via Gcc wrote:
>
> > I don't see why it should not apply to void*. memcpy(3) should get this
> > attribute:
> >
> > [[alx::restrict(1)]]
> > [[alx::restrict(2)]]
> > void
On Fri, 26 Jul 2024, Alejandro Colomar via Gcc wrote:
> I don't see why it should not apply to void*. memcpy(3) should get this
> attribute:
>
> [[alx::restrict(1)]]
> [[alx::restrict(2)]]
> void *memcpy(void *dst, const void *src, size_t n);
That would disallow copying betwee
Hi Joseph,
On Fri, Jul 26, 2024 at 04:24:14PM GMT, Joseph Myers wrote:
> On Wed, 10 Jul 2024, Alejandro Colomar via Gcc wrote:
>
> >6.7.13.x The restrict function attribute
> > Constraints
> > The restrict attribute shall be applied to a function.
> >
> > A 1‐bas
Hi Branden!
On Fri, Jul 26, 2024 at 11:35:51AM GMT, G. Branden Robinson wrote:
> At 2024-07-26T16:24:14+, Joseph Myers wrote:
> > I know that "noalias" was included in some C89 drafts but removed from
> > the final standard after objections. Maybe someone who was around
> > then could explain
On 7/26/24 09:24, Joseph Myers wrote:
Maybe someone who was around then could
explain what "noalias" was, what the problems with it were and how it
differs from "restrict"
You can get a hint by reading Dennis Ritchie's 1988 email with the
unforgettable bottom line "Noalias must go. This is n
At 2024-07-26T16:24:14+, Joseph Myers wrote:
> I know that "noalias" was included in some C89 drafts but removed from
> the final standard after objections. Maybe someone who was around
> then could explain what "noalias" was, what the problems with it were
For this part, I think the source m
On Wed, 10 Jul 2024, Alejandro Colomar via Gcc wrote:
>6.7.13.x The restrict function attribute
> Constraints
> The restrict attribute shall be applied to a function.
>
> A 1‐based index can be specified in an attribute argument
> clause, to associ
http://click.campaign.triomasters.com/?qs=5a121056e622108f021623cff235bd781402d61a7bdecc7506511887a0c23b17f597f8171a17528e4896a1f5edf2f294167df33135028bed
Intermediate Payroll for the Administrative Professional
Wednesday, August 07, 2024 | EST: 12:30 PM | PST: 09:30 AM
Introduction
On Thu, Jul 25, 2024 at 3:36 PM Prathamesh Kulkarni via Gcc
wrote:
>
> Hi,
> I am working on enabling offloading to nvptx from AAarch64 host. As mentioned
> on wiki (https://gcc.gnu.org/wiki/Offloading#Running_.27make_check.27),
> I ran make check-target-libgomp on AAarch64 host (and no GPU) with
15 matches
Mail list logo
