Re: RFC: Formalization of the Intel assembly syntax (PR53929)

2024-01-29 Thread Hans-Peter Nilsson
On Fri, 19 Jan 2024, LIU Hao wrote: > ? 2024-01-18 20:54, Jan Beulich ??: > > I'm sorry, but most of your proposal may even be considered for being > > acceptable only if you would gain buy-off from the MASM guys. Anything > > MASM treats as valid ought to be permitted by gas as well (within the >

[Patch, stage-1, RFC]: i386: attribute regparm/stdcall and vaargs

2024-01-29 Thread Bernhard Reutner-Fischer via Gcc
[I was torn towards asking gcc@ only, individual i386 maintainers in private or bluntly asking for help on gcc-patches or re-iterate through ABI, so in an attempt to cut off years of latency i hereby ask all and everybody for assistance. Stage4 means any chances are low, i know.. hence stage 1 mate

Re: contributing advice

2024-01-29 Thread Jonathan Wakely via Gcc
On Mon, 29 Jan 2024 at 20:25, Ed wrote: > > > On Monday, January 29, 2024 at 03:13:07 PM EST, Jonathan Wakely via Gcc > wrote: > > > On Mon, 29 Jan 2024 at 19:15, Claudio Bantaloukas via Gcc > wrote: > > > > On 26/01/2024 17:51, Florin Mateoc via Gcc wrote: > > > Hi all, > > > > > > I am an expe

Re: contributing advice

2024-01-29 Thread 3dw4rd--- via Gcc
3dw...@verizon.net On Monday, January 29, 2024 at 03:13:07 PM EST, Jonathan Wakely via Gcc wrote: On Mon, 29 Jan 2024 at 19:15, Claudio Bantaloukas via Gcc wrote: > > On 26/01/2024 17:51, Florin Mateoc via Gcc wrote: > > Hi all, > > > > I am an experienced software developer, with

Re: contributing advice

2024-01-29 Thread Jonathan Wakely via Gcc
On Mon, 29 Jan 2024 at 19:15, Claudio Bantaloukas via Gcc wrote: > > On 26/01/2024 17:51, Florin Mateoc via Gcc wrote: > > Hi all, > > > > I am an experienced software developer, with an interest in compilers, and > > an admirer of gcc. > > I would like to contribute, hopefully reusing some of my

Re: contributing advice

2024-01-29 Thread Claudio Bantaloukas via Gcc
On 26/01/2024 17:51, Florin Mateoc via Gcc wrote: > Hi all, > > I am an experienced software developer, with an interest in compilers, and > an admirer of gcc. > I would like to contribute, hopefully reusing some of my existing skills, > experience and interests, but unfortunately the (current) ov

Re: Lenient overhead resolutions and where to find them in the manual

2024-01-29 Thread Jonathan Wakely via Gcc
On Mon, 29 Jan 2024, 18:24 Jonathan Wakely, wrote: > > > On Mon, 29 Jan 2024, 18:17 Martin Licht via Gcc, wrote: > >> GCC seems to have a non-standard lenient C++ overload resolution that is >> not documented (or easy to find in the manual). >> >> The following C++ code compiles with GCC. Howeve

Re: Lenient overhead resolutions and where to find them in the manual

2024-01-29 Thread Jonathan Wakely via Gcc
On Mon, 29 Jan 2024, 18:17 Martin Licht via Gcc, wrote: > GCC seems to have a non-standard lenient C++ overload resolution that is > not documented (or easy to find in the manual). > > The following C++ code compiles with GCC. However, it produces a warning > about an ambiguous overload that appa

Lenient overhead resolutions and where to find them in the manual

2024-01-29 Thread Martin Licht via Gcc
GCC seems to have a non-standard lenient C++ overload resolution that is not documented (or easy to find in the manual). The following C++ code compiles with GCC. However, it produces a warning about an ambiguous overload that apparently is not acceptable by the standard. Clang and MVSC simply