Re: GCC Mission Statement

On 6/9/21 7:09 AM, Valentino Giudice via Gcc wrote: If the Steering Committee updates the mission statement, it may appear that the mission statement follows the decisions of the steering committee (in place of the contrary). In that case, what would be the purpose of a mission statement? In es

Re: GCC Mission Statement

Hi Gabriel, On Wed, 9 Jun 2021 11:44:10 +0200 Gabriel Ravier via Gcc wrote: > Speaking on the "change it recklessly" issue, I would personally say > that SC has indeed arguably done this [...] > some people threatened to pull away from GCC entirely if it remained > tied to the FSF. I personally h

replacing the backwards threader and more

Hi Jeff. Hi folks. What started as a foray into severing the old (forward) threader's dependency on evrp, turned into a rewrite of the backwards threader code. I'd like to discuss the possibility of replacing the current backwards threader with a new one that gets far more threads and can p

Re: replacing the backwards threader and more

On Wed, Jun 9, 2021 at 1:50 PM Aldy Hernandez via Gcc wrote: > > Hi Jeff. Hi folks. > > What started as a foray into severing the old (forward) threader's > dependency on evrp, turned into a rewrite of the backwards threader > code. I'd like to discuss the possibility of replacing the current >

Re: GCC Mission Statement

On 6/9/21 12:11 PM, Giacomo Tesio wrote: Hi Gabriel, On Wed, 9 Jun 2021 11:44:10 +0200 Gabriel Ravier via Gcc wrote: Speaking on the "change it recklessly" issue, I would personally say that SC has indeed arguably done this [...] some people threatened to pull away from GCC entirely if it remai

GNAT Reference Manual: Typos in chapter 1

I've found some typos, etc. in chapter 1 ("About This Guide") of the GNAT Reference Manual. Here they come in order of appearance: #1 This manual contains useful information in writing programs using the GNAT compiler. s/in writing/on writing #2 It includes information on implementati

Mission Statement

All this could became meaningless in ten years time because major changes have resulted from division. If we go on dividing the world using a knife rather than stitching it together, everything will be left in tatters. The more effort taken in this direction, the more destructive things will beco

Re: Mission Statement

On Jun 9, 2021, at 6:48 AM, Christopher Dimech via Gcc mailto:gcc@gcc.gnu.org>> wrote > All this could became meaningless in ten years time because major > changes have resulted from division. If we go on dividing the > world using a knife rather than stitching it together, everything > will be le

Re: GCC Mission Statement

Hi Gabriel, On June 9, 2021 12:41:09 PM UTC, Gabriel Ravier wrote: > > I do consider that a lack of transparency is pretty bad, and that > discussions on subjects like this should be done in public, but I > wouldn't say it's just as bad as the potential risk that a fork would > incur. I reall

Re: GCC Mission Statement

On Wed, Jun 9, 2021 at 4:22 PM Giacomo Tesio wrote: > > Hi Gabriel, > > On June 9, 2021 12:41:09 PM UTC, Gabriel Ravier > wrote: > > > > I do consider that a lack of transparency is pretty bad, and that > > discussions on subjects like this should be done in public, but I > > wouldn't say it's ju

Re: GCC Mission Statement

Sure Richard, I know. On June 9, 2021 2:32:22 PM UTC, Richard Biener wrote: > > You are free to create "DCO-free" branches for the GCC 11 series > (and older), reverting any DCO "incumbered" backports that reach > the official GCC branches for those series. I could. Like all other people aff

Re: replacing the backwards threader and more

On 6/9/21 2:09 PM, Richard Biener wrote: On Wed, Jun 9, 2021 at 1:50 PM Aldy Hernandez via Gcc wrote: Hi Jeff. Hi folks. What started as a foray into severing the old (forward) threader's dependency on evrp, turned into a rewrite of the backwards threader code. I'd like to discuss the po

GCC Mission Statement

> Sent: Thursday, June 10, 2021 at 3:26 AM > From: "Giacomo Tesio" > To: "Richard Biener" > Cc: "gcc@gcc.gnu.org" , "Valentino Giudice" > > Subject: Re: GCC Mission Statement > > Sure Richard, I know. > > On June 9, 2021 2:32:22 PM UTC, Richard Biener wrote: > > > > You are free to create "D

Re: Mission Statement

On Jun 9, 2021, at 8:30 AM, Christopher Dimech wrote: > > Besides inspiring a sceptic attitude, Cicero made the language of > the civilized world. Yes > This has nothing to do with any complaints > of mistreatment, but mostly about belief systems that have taken > over many people's lives. Tha

Re: replacing the backwards threader and more

On June 9, 2021 5:34:03 PM GMT+02:00, Aldy Hernandez wrote: > > >On 6/9/21 2:09 PM, Richard Biener wrote: >> On Wed, Jun 9, 2021 at 1:50 PM Aldy Hernandez via Gcc > wrote: >>> >>> Hi Jeff. Hi folks. >>> >>> What started as a foray into severing the old (forward) threader's >>> dependency on evrp,

Empty structures extensions

Should the docs at https://gcc.gnu.org/onlinedocs/gcc/Empty-Structures.html mention that you can use {} to initialize such structs?

Dear Hohnka M.J., Miller J.A., Dacumos K.M., Fritton T.J., Erdley J.D., Long L.N.: Ԝеlϲomе to Сontrіbսte Your Original Manսsᴄriрts - Evaluation of compiler-induced vulnerabilities

If you no longer wish to receive such kind of еmаіls from us, you can ᴄliᴄκ here to unѕuƄѕcriƄе. Jοᴜrnаl of Electrical and Electronic Engineering ІЅЅΝ Online: ᒿЗᒿ9-160ƼІЅЅΝ Print: ᒿЗᒿ9-161З Jοᴜrnаl of Electrical and Electronic Engineering is a peer-rеvіеwed an

Re: replacing the backwards threader and more

On 6/9/2021 9:34 AM, Aldy Hernandez wrote: On 6/9/21 2:09 PM, Richard Biener wrote: On Wed, Jun 9, 2021 at 1:50 PM Aldy Hernandez via Gcc wrote: Hi Jeff.  Hi folks. What started as a foray into severing the old (forward) threader's dependency on evrp, turned into a rewrite of the backwa

Re: replacing the backwards threader and more

On 6/9/21 9:47 PM, Jeff Law wrote: On 6/9/2021 9:34 AM, Aldy Hernandez wrote: On 6/9/21 2:09 PM, Richard Biener wrote: On Wed, Jun 9, 2021 at 1:50 PM Aldy Hernandez via Gcc wrote: Hi Jeff.  Hi folks. What started as a foray into severing the old (forward) threader's dependency on evr

Re: replacing the backwards threader and more

On 6/9/2021 2:39 PM, Aldy Hernandez wrote: On 6/9/21 9:47 PM, Jeff Law wrote: On 6/9/2021 9:34 AM, Aldy Hernandez wrote: On 6/9/21 2:09 PM, Richard Biener wrote: On Wed, Jun 9, 2021 at 1:50 PM Aldy Hernandez via Gcc wrote: Hi Jeff.  Hi folks. What started as a foray into severing

Mission Statement

> Sent: Thursday, June 10, 2021 at 3:49 AM > From: "Aaron Gyes via Gcc" > To: "GCC Administrator via Gcc" > Subject: Re: Mission Statement > > On Jun 9, 2021, at 8:30 AM, Christopher Dimech wrote: > > > > Besides inspiring a sceptic attitude, Cicero made the language of > > the civilized worl

Re: Mission Statement

> In this state of making something right, and making > something wrong, there is no way for inclusiveness. Are you familiar with the tolerance paradox? Aaron

Licensing Complications

A thing to seriously tackle is how the Gnu GPL permits making a modified version and letting the public access it on a server without ever releasing its source code. The focus must really be on ending any ownership on software. This problem necessitates the production of additional legal instrume

Mission Statement

> Sent: Thursday, June 10, 2021 at 9:07 AM > From: "Aaron Gyes via Gcc" > To: "GCC Administrator via Gcc" > Subject: Re: Mission Statement > > > In this state of making something right, and making > > something wrong, there is no way for inclusiveness. > > Are you familiar with the tolerance para

Re: git gcc-commit-mklog doesn't extract PR number to ChangeLog

Sorry, should be sent to this mail-list. On 2021/6/10 11:31, Xionghu Luo via Gcc-patches wrote: Hi, I noticed that the "git gcc-commit-mklog" command doesn't extract PR number from title to ChangeLog automatically, then the committed patch doesn't update the related bugzilla PR website after ch

Re: git gcc-commit-mklog doesn't extract PR number to ChangeLog

On 6/10/21 7:22 AM, Xionghu Luo wrote: Sorry, should be sent to this mail-list. On 2021/6/10 11:31, Xionghu Luo via Gcc-patches wrote: Hi, I noticed that the "git gcc-commit-mklog" command doesn't extract PR number from title to ChangeLog automatically, then the committed patch doesn't update

Re: git gcc-commit-mklog doesn't extract PR number to ChangeLog

On 2021/6/10 14:17, Martin Liška wrote: > On 6/10/21 7:22 AM, Xionghu Luo wrote: >> Sorry, should be sent to this mail-list. >> >> >> On 2021/6/10 11:31, Xionghu Luo via Gcc-patches wrote: >>> Hi, >>> I noticed that the "git gcc-commit-mklog" command doesn't extract PR >>> number from title to C

Re: git gcc-commit-mklog doesn't extract PR number to ChangeLog

On 10.06.21 08:17, Martin Liška wrote: Yes, we currently only support automatic extraction from comments from test-cases. How does your commit title look like? Note that we require bugzilla components being part of PR entry, which is not commonly used in git titles due to length limitation. On