On Mon, Nov 04, 2024 at 01:36:56PM -0500, Jason Merrill wrote:
> On 11/3/24 12:26 PM, Paul Iannetta wrote:
> > On Fri, Nov 01, 2024 at 11:45:07AM -0400, Jason Merrill wrote:
> > > On 10/31/24 6:43 AM, Paul Iannetta wrote:
> > > > gcc/c-family/ChangeLog:
> >
On Fri, Nov 01, 2024 at 11:45:07AM -0400, Jason Merrill wrote:
> On 10/31/24 6:43 AM, Paul Iannetta wrote:
> > gcc/c-family/ChangeLog:
> >
> > * c-pragma.cc (struct pragma_pp_data): Use (struct
> > internal_pragma_handler);
> > (c_register_pragma_1): A
gcc/c-family/ChangeLog:
* c-pragma.cc (struct pragma_pp_data): Use (struct
internal_pragma_handler);
(c_register_pragma_1): Always register name and space for all pragmas.
(c_invoke_pragma_handler): Adapt.
(c_invoke_early_pragma_handler): Likewise.
(c_pp_in
From: Paul Iannetta
Hi,
Currently, the way pragmas are registered is a bit different depending on
whether gcc is performing preprocessing only. This patch harmonizes both
behaviors and registers the name and space of all pragmas in all cases, and not
only the handler when not in pre-processing
Ping (https://gcc.gnu.org/pipermail/gcc-patches/2024-September/662211.html)
On Wed, Sep 04, 2024 at 01:56:59PM +0200, Paul Iannetta wrote:
> Hi,
>
> Currently, the only pragma directives that can be added by a backend, only
> have
> access to the information on the same lin
Hi,
Currently, the only pragma directives that can be added by a backend, only have
access to the information on the same line as the pragma, which is enough for
modifying a global state.
This means that a loop target pragma could look like this:
#pragma target begin keyword [options]
#pragma ta
Hi,
I would like to add myself to write after approval, is it ok for
master?
Thanks,
Paul Iannetta
---8<---
ChangeLog:
* MAINTAINERS: Add myself to write after approval
Signed-off-by: Paul Iannetta
---
MAINTAINERS | 1 +
ite after approval".
> Sure. I'd sponsor them.
Thanks. May I request an account on sourceware.org, mentioning you as
our sponsor?
Paul
>From ce418afa1d3098603e26e1fd2ee262a8ab72e5ab Mon Sep 17 00:00:00 2001
From: Paul Iannetta
Date: Tue, 24 Oct 2023 09:48:42 +0200
Subject: [PAT
On Tue, Sep 26, 2023 at 08:29:11AM -0600, Jeff Law wrote:
>
>
> On 9/25/23 03:55, Paul Iannetta wrote:
> > On Mon, Sep 18, 2023 at 08:39:34AM +0200, Paul Iannetta wrote:
> > > On Thu, Sep 14, 2023 at 04:24:33PM +0200, Paul Iannetta wrote:
> > > > Hi,
>
On Mon, Sep 18, 2023 at 08:39:34AM +0200, Paul Iannetta wrote:
> On Thu, Sep 14, 2023 at 04:24:33PM +0200, Paul Iannetta wrote:
> > Hi,
> >
> > This is a small patch so that both dg-extract-results.py and
> > dg-extract-results.sh share the same header. In particular,
On Thu, Sep 14, 2023 at 04:24:33PM +0200, Paul Iannetta wrote:
> Hi,
>
> This is a small patch so that both dg-extract-results.py and
> dg-extract-results.sh share the same header. In particular, it fixes
> the fact that the regexp r'^Test Run By (\S+) on (.*)$' was neve
Hi,
This is a small patch so that both dg-extract-results.py and
dg-extract-results.sh share the same header. In particular, it fixes
the fact that the regexp r'^Test Run By (\S+) on (.*)$' was never
matched in the python file.
Thanks,
--
Paul
Kalray
Author: Paul Iannetta
Date:
ializing argument 1 of ‘int f(int*)’
}
Thanks,
Paul
Rebased on current trunk, bootstrapped and regtested.
# >8
gcc/cp/ChangeLog:
2022-11-09 Paul Iannetta
* call.cc (convert_like_internal): Add support for implicit
convers
On Thu, Nov 03, 2022 at 02:38:39PM +0100, Georg-Johann Lay wrote:
> > [PATCH v3] c++: parser - Support for target address spaces in C++
>
> First of all, it is great news that GCC is going to implement named address
> spaces for C++.
>
> I have some questions:
>
> 1. How is name-mangling going t
On Wed, Oct 19, 2022 at 02:55:21PM -0400, Jason Merrill wrote:
> On 10/18/22 13:01, Paul Iannetta wrote:
> > Thank you very much for the detailed review.
> >
> > On Tue, Oct 18, 2022 at 10:24:23AM -0400, Jason Merrill wrote:
> > > On 10/18/22 03:37, Paul Iannetta
On Wed, Oct 19, 2022 at 09:24:06AM +0200, Martin Liška wrote:
> On 10/17/22 16:16, Paul Iannetta wrote:
> > Hi Martin,
> >
> > Thank you very much for porting the documentation to Sphinx, it is
> > very convenient to use, especially the menu on the left and the
> >
Thank you very much for the detailed review.
On Tue, Oct 18, 2022 at 10:24:23AM -0400, Jason Merrill wrote:
> On 10/18/22 03:37, Paul Iannetta wrote:
> > On Fri, Oct 14, 2022 at 11:19:50AM -0400, Jason Merrill wrote:
> > > On 10/13/22 17:57, Paul Iannetta wrote:
> > > &
On Mon, Oct 17, 2022 at 09:22:23AM +0200, Richard Biener wrote:
> On Fri, Oct 14, 2022 at 4:18 PM Paul Iannetta via Gcc-patches
> wrote:
> >
> > On Wed, Oct 12, 2022 at 01:18:19AM +0200, Paul Iannetta wrote:
> > > On Mon, Oct 10, 2022 at 11:07:06PM +, Joseph Myer
On Fri, Oct 14, 2022 at 11:19:50AM -0400, Jason Merrill wrote:
> On 10/13/22 17:57, Paul Iannetta wrote:
> > On Thu, Oct 13, 2022 at 03:41:16PM -0400, Jason Merrill wrote:
> > > On 10/13/22 12:02, Paul Iannetta wrote:
> > > > On Thu, Oct 13, 2022 at 11:47:4
Hi Martin,
Thank you very much for porting the documentation to Sphinx, it is
very convenient to use, especially the menu on the left and the
search bar.
However, I also regularly browse and search the documentation through
info, especially when I want to use regexps to search or need to
include
On Wed, Oct 12, 2022 at 01:18:19AM +0200, Paul Iannetta wrote:
> On Mon, Oct 10, 2022 at 11:07:06PM +, Joseph Myers wrote:
> > On Mon, 10 Oct 2022, Paul Iannetta via Gcc-patches wrote:
> >
> > > I have a patch to bring this feature to the C front-end as well, and
>
On Thu, Oct 13, 2022 at 03:41:16PM -0400, Jason Merrill wrote:
> On 10/13/22 12:02, Paul Iannetta wrote:
> > On Thu, Oct 13, 2022 at 11:47:42AM -0400, Jason Merrill wrote:
> > > On 10/13/22 11:23, Paul Iannetta wrote:
> > > > On Thu, Oct 13, 2022 at 11:02:2
On Thu, Oct 13, 2022 at 11:47:42AM -0400, Jason Merrill wrote:
> On 10/13/22 11:23, Paul Iannetta wrote:
> > On Thu, Oct 13, 2022 at 11:02:24AM -0400, Jason Merrill wrote:
> > > On 10/12/22 20:52, Paul Iannetta wrote:
> > > > On Tue, Oct 11, 2022 at 09:49:4
On Thu, Oct 13, 2022 at 11:02:24AM -0400, Jason Merrill wrote:
> On 10/12/22 20:52, Paul Iannetta wrote:
> > On Tue, Oct 11, 2022 at 09:49:43PM -0400, Jason Merrill wrote:
> > >
> > > It surprises that this is the only place we complain about an object with
> > &
On Thu, Oct 13, 2022 at 07:46:46AM +0200, Jakub Jelinek wrote:
> On Thu, Oct 13, 2022 at 02:52:59AM +0200, Paul Iannetta via Gcc-patches wrote:
> > + if (type != error_mark_node
> > + && !ADDR_SPACE_GENERIC_P
On Tue, Oct 11, 2022 at 09:49:43PM -0400, Jason Merrill wrote:
>
> It surprises that this is the only place we complain about an object with an
> address-space qualifier. Shouldn't we also complain about e.g. automatic
> variables/parameters or non-static data members with address-space qualified
On Mon, Oct 10, 2022 at 11:07:06PM +, Joseph Myers wrote:
> On Mon, 10 Oct 2022, Paul Iannetta via Gcc-patches wrote:
>
> > I have a patch to bring this feature to the C front-end as well, and
> > would like to hear your opinion on it, especially since it may affect
> >
Thank you very much for the comments.
On Mon, Oct 10, 2022 at 03:20:13PM -0400, Jason Merrill wrote:
> On 10/9/22 12:12, Paul Iannetta wrote:
> > That's a nice feature! LLVM is using AS to mangle the
> > address-name qualified types but that would have required an updat
Hi Ian,
Observations are also very welcomed, thank you!
On Mon, Oct 10, 2022 at 03:37:24PM +0100, Iain Sandoe wrote:
> Hi Paul,
>
> Not a review of the patch - but a couple of observations.
>
> > On 10 Oct 2022, at 15:11, Paul Iannetta via Gcc-patches
> > wrote:
>
Hi,
I am trying to bridge the gap between the extensions supported by the C
and C++ front-ends. When it comes to vector extensions, C++ supports
vectors in comparisons and within conditional expressions whereas the C
front-end does not.
I have a patch to bring this feature to the C front-end as
Hi,
On Thu, Oct 06, 2022 at 01:34:40PM -0400, Jason Merrill wrote:
[snip]
>
> Hmm? We mangle __restrict:
>
> void f(int *__restrict *p) { } // _Z1fPrPi
>
Indeed, I have overlooked that point. Thank you for pointing it out.
> but cv-qualifiers (including restrict) are dropped on the top-leve
mangler ignores address spaces, much like
it ignores __restrict__.
Depending on the reception, I'll add further testcases and will update
the relevant part of the documentation.
Cheers,
Paul
Author: Paul Iannetta
Date: Wed Oct 5 16:44:36 2022 +0200
Add support for custom addres
AN_INSN
mips_final_postscan_insn
```
reveals that m68k, avr and mips are the only affected targets upstream.
Paul Iannetta
Kalray
_final_postscan_insn
```
reveals that m68k, avr and mips are the only affected targets upstream.
Paul Iannetta
Kalray
0001-postscan_insn-hook-not-called-after-input_asm.patch
Description: application/mbox
34 matches
Mail list logo
