RE: GCC Decimal128 class

2024-01-23 Thread Ming Cheng via Gcc
https://gcc.gnu.org/onlinedocs/gcc-13.2.0/libstdc++/api/a10385.html should be the latest. I thought there is a std::string/char* constructor. -Original Message- From: Ming Cheng Sent: Wednesday, January 24, 2024 2:20 PM To: Jonathan Wakely Cc: GCC Development Subject: RE: GCC Decimal128

Re: GSoc Topics

2024-01-23 Thread Gaurang Aswal via Gcc
Thanks, I'll check them out. On Wed, 24 Jan, 2024, 03:52 Martin Jambor, wrote: > Hello, > > We are delighted you found contributing to GCC interesting. GCC has > applied to be part of GSoC 2024 but of course selected organizations > have not been announced yet. > > On Fri, Jan 12 2024, Gaurang

Re: [PATCH 5/4] libbacktrace: improve getting debug information for loaded dlls

2024-01-23 Thread Ian Lance Taylor via Gcc
On Thu, Jan 4, 2024 at 2:33 PM Björn Schäpers wrote: > > Am 03.01.2024 um 00:12 schrieb Björn Schäpers: > > Am 30.11.2023 um 20:53 schrieb Ian Lance Taylor: > >> On Fri, Jan 20, 2023 at 2:55 AM Björn Schäpers wrote: > >>> > >>> From: Björn Schäpers > >>> > >>> Fixes https://github.com/ianlanceta

Re: GSoc Topics

2024-01-23 Thread Martin Jambor
Hello, We are delighted you found contributing to GCC interesting. GCC has applied to be part of GSoC 2024 but of course selected organizations have not been announced yet. On Fri, Jan 12 2024, Gaurang Aswal via Gcc wrote: > Hey I am Gaurang Aswal a 4th year B.E. Computer Science student from BI

Re: [PATCH 4/4] libbacktrace: get debug information for loaded dlls

2024-01-23 Thread Björn Schäpers
Am 03.01.2024 um 00:12 schrieb Björn Schäpers: Am 30.11.2023 um 20:53 schrieb Ian Lance Taylor: On Fri, Jan 20, 2023 at 2:55 AM Björn Schäpers wrote: From: Björn Schäpers Fixes https://github.com/ianlancetaylor/libbacktrace/issues/53, except that libraries loaded after the backtrace_initial

Re: GCC Decimal128 class

2024-01-23 Thread Jonathan Wakely via Gcc
On Tue, 23 Jan 2024 at 14:16, Jonathan Wakely wrote: > > On Tue, 23 Jan 2024 at 02:01, Ming Cheng via Gcc wrote: > > > > Hi GCC, > > > > Seems Janis is not at IBM. Wondering someone from GCC can help my question? > > > > Thanks > > Ming. > > > > From: Ming Cheng > > Sent: Monday, January 22, 2024

Re: GCC Decimal128 class

2024-01-23 Thread Jonathan Wakely via Gcc
On Tue, 23 Jan 2024 at 02:01, Ming Cheng via Gcc wrote: > > Hi GCC, > > Seems Janis is not at IBM. Wondering someone from GCC can help my question? > > Thanks > Ming. > > From: Ming Cheng > Sent: Monday, January 22, 2024 3:18 PM > To: janis...@us.ibm.com > Subject: GCC Decimal128 class > > Hi Jani

Re: Mystery instructions

2024-01-23 Thread Alex Huang via Gcc
Hi, These instructions looks to be part of the T-head vendor extension instruction set. With the spec here https://github.com/T-head-Semi/thead-extension-spec. Best regards Alex > On Jan 23, 2024, at 8:42 AM, jacob navia via Gcc wrote: > > Hi > The GNU assembler supports two instructions fo

Mystery instructions

2024-01-23 Thread jacob navia via Gcc
Hi The GNU assembler supports two instructions for the T-Head risk machines called: th.ipop th.ipush With no arguments. These instructions (they are no macros or aliases) are UNDOCUMENTED in the T-Head instruction manuals that I have, and a google search yields absolutely nothing. Can anyone h

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

2024-01-23 Thread Jan Beulich via Gcc
On 23.01.2024 10:21, LIU Hao wrote: > 在 2024-01-23 17:03, Jan Beulich 写道: >> Hmm, that would suggest to me that the Dwarf code abuses the interface. >> A "name" certainly shouldn't be an expression. And hence the result of >> the example ought to be >> >> .long "LXXYY"-1# "LXXYY" minus on

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

2024-01-23 Thread LIU Hao via Gcc
在 2024-01-23 17:03, Jan Beulich 写道: Hmm, that would suggest to me that the Dwarf code abuses the interface. A "name" certainly shouldn't be an expression. And hence the result of the example ought to be .long "LXXYY"-1# "LXXYY" minus one So I shouldn't have checked for `*` right? Th

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

2024-01-23 Thread Jan Beulich via Gcc
On 23.01.2024 10:00, LIU Hao wrote: > 在 2024-01-23 16:38, Jan Beulich 写道: >> Right, but this is very "draft". You can't blindly assume the gas you use >> actually can deal with quotation. > > Let's assume that for the time being, but there's something else; see below. > > >>> .refptr.bx: >>>

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

2024-01-23 Thread LIU Hao via Gcc
在 2024-01-23 16:38, Jan Beulich 写道: Right, but this is very "draft". You can't blindly assume the gas you use actually can deal with quotation. Let's assume that for the time being, but there's something else; see below. .refptr.bx: .quad bx Sure, this one needs quoting then, t

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

2024-01-23 Thread Jan Beulich via Gcc
On 23.01.2024 02:27, LIU Hao wrote: > 在 2024-01-22 16:39, Jan Beulich 写道: >> Right, I did some work in that direction a while ago. But iirc there are >> still cases left to be addressed. > > Attached is a draft patch for GCC, bootstrapped on {i686,x86_64}-w64-mingw32 > with GCC 13.2 and > binuti