Re: Naming flag for specifying the output file name for Binary Module Interface files

2022-12-14 Thread chuanqi.xcq via Gcc
Hi David, > I think Nathan might've been asking not only about what currently happens, but what we think should happen? Yes. > Is that consistent with `-o`? (I assume so, but don't know - I guess there aren't many cases where `-o` is unused (maybe `-fsyntax-only`), so that behavior might be a bit l

Re: Possible regression in DF analysis

2022-12-14 Thread Claudiu Zissulescu Ianculescu via Gcc
I have update the fix to this one: diff --git a/gcc/df-core.cc b/gcc/df-core.cc index a901b84878f..cc6383990a1 100644 --- a/gcc/df-core.cc +++ b/gcc/df-core.cc @@ -1437,7 +1437,16 @@ df_analyze_loop (class loop *loop) df_set_blocks (blocks); BITMAP_FREE (blocks); - df_analyze_1 (); + /* I

Re: Possible regression in DF analysis

2022-12-14 Thread Richard Biener via Gcc
On Wed, Dec 14, 2022 at 11:37 AM Claudiu Zissulescu Ianculescu wrote: > > I have update the fix to this one: > > diff --git a/gcc/df-core.cc b/gcc/df-core.cc > index a901b84878f..cc6383990a1 100644 > --- a/gcc/df-core.cc > +++ b/gcc/df-core.cc > @@ -1437,7 +1437,16 @@ df_analyze_loop (class loop *

Re: Possible regression in DF analysis

2022-12-14 Thread Claudiu Zissulescu Ianculescu via Gcc
Hi Richard, Sorry for my misunderstanding. I am calling the df_analyze() instead of df_analyze1() at the end. Shouldn't df_analyze take care and compute the correct postorder (df-core.cc:1273) ? Thank you, Claudiu On Wed, Dec 14, 2022 at 1:06 PM Richard Biener wrote: > > On Wed, Dec 14, 2022 a

Re: Possible regression in DF analysis

2022-12-14 Thread Richard Biener via Gcc
On Wed, Dec 14, 2022 at 12:30 PM Claudiu Zissulescu Ianculescu wrote: > > Hi Richard, > > Sorry for my misunderstanding. I am calling the df_analyze() instead > of df_analyze1() at the end. Shouldn't df_analyze take care and > compute the correct postorder (df-core.cc:1273) ? The point of df_ana

[RISC-V] [SIG-toolchain] Meeting will be canceled (Dec 15, 2022)

2022-12-14 Thread jiawei
Hi all, Tomorrow's meeting will be canceled, since there was few new topics to discuss. The next RISC-V GNU Toolchain meeting is collecting. Please let me know if you have any topics want to discuss in the next meeting. Best Regards, Jiawei

Energy Exchange 2022 Attendees

2022-12-14 Thread Laura Prickett via Gcc
Hi, Would you be interested in obtaining the Energy Exchange 2022 attendance database? Facility managers, Fleet managers, Water managers, State resource managers, City planners, Procurement officers, Building commissioners, Project implementation specialists, Energy auditors, Compliance man

Contribution

2022-12-14 Thread Mohamed Atef via Gcc
Hello all, As I mentioned before, I don't have much time to contribute. So is there any way I can contribute some medium project I can work on but myself in the long run? I loved this community, I contributed before so can you suggest some work for me? Mohamed

Possible dead code in file lra-spills.cc

2022-12-14 Thread G.T. via Gcc
At line 276, lra_assert (spill_class != NO_REGS); would trigger whenever execution reached here with spill_class equal to NO_REGS. Seems to me that would never happen. Because one of the conditions in the if statement right above it (line 265) catches spill_class == NO_REGS and causes the rest of t

Re: Naming flag for specifying the output file name for Binary Module Interface files

2022-12-14 Thread David Blaikie via Gcc
On Wed, Dec 14, 2022 at 1:56 AM chuanqi.xcq wrote: > > Hi David, > > > I think Nathan might've been asking not only about what currently > happens, but what we think should happen? > > Yes. > > > Is that consistent with `-o`? (I assume so, but don't know - I guess > there aren't many cases where `

Re: Possible dead code in file lra-spills.cc

2022-12-14 Thread Richard Biener via Gcc
> Am 14.12.2022 um 18:28 schrieb G.T. via Gcc : > > At line 276, lra_assert (spill_class != NO_REGS); would trigger > whenever execution reached here with spill_class equal to NO_REGS. > Seems to me that would never happen. Because one of the conditions in > the if statement right above it (li

Re: Naming flag for specifying the output file name for Binary Module Interface files

2022-12-14 Thread Nathan Sidwell via Gcc
I'm missing something from this discussion. IIUC the claim is that these 2 new options -fmodule-output{,=NAME} are for build systems that want to specify the module output file. But how do they specify the mapping from module/header-unit name to CMI, so that imports work? Is this really a c

[-Wstringop-overflow=] strncat(3)

2022-12-14 Thread Alejandro Colomar via Gcc
Hi, I was rewriting the strncat(3) manual page, and when I tried to compile the example program, I got a surprise from the compiler. Here goes the page: strncat(3) Library Functions Manual strncat(3) NAME strncat - concatenate a null‐padded chara

Re: [-Wstringop-overflow=] strncat(3)

2022-12-14 Thread Alejandro Colomar via Gcc
On 12/14/22 23:45, Alejandro Colomar wrote: Hi, I was rewriting the strncat(3) manual page, and when I tried to compile the example program, I got a surprise from the compiler. Here goes the page:   strncat(3)   Library Functions Manual  strncat(3)   NAME  

Re: [-Wstringop-overflow=] strncat(3)

2022-12-14 Thread Alejandro Colomar via Gcc
On 12/14/22 23:51, Alejandro Colomar wrote: On 12/14/22 23:45, Alejandro Colomar wrote: Hi, I was rewriting the strncat(3) manual page, and when I tried to compile the example program, I got a surprise from the compiler. Here goes the page:    strncat(3)   Library Functions

Re: [-Wstringop-overflow=] strncat(3)

2022-12-14 Thread Andrew Pinski via Gcc
On Wed, Dec 14, 2022 at 2:46 PM Alejandro Colomar via Libc-alpha wrote: > > Hi, > > I was rewriting the strncat(3) manual page, and when I tried to compile the > example program, I got a surprise from the compiler. > > Here goes the page: > > >strncat(3) Library Functions Manual

Re: [-Wstringop-overflow=] strncat(3)

2022-12-14 Thread Alejandro Colomar via Gcc
[CC += groff] Hi Andrew, On 12/14/22 23:57, Andrew Pinski wrote: On Wed, Dec 14, 2022 at 2:46 PM Alejandro Colomar via Libc-alpha wrote: Hi, I was rewriting the strncat(3) manual page, and when I tried to compile the example program, I got a surprise from the compiler. Here goes the page:

Re: Naming flag for specifying the output file name for Binary Module Interface files

2022-12-14 Thread chuanqi.xcq via Gcc
Hi Nathan, > But how do they specify the mapping from module/header-unit name to CMI, so > that > imports work? > > Is this really a clang-specific mechanism, as it has no module mapper ATM > (IIUC)? Yes, clang doesn't have a module mapper. And I remember Iain said he want to introduce these op

Why does filing a bug report have to be so damn hard?

2022-12-14 Thread Barry Manilowa via Gcc
Seriously? You UNIX folks are completely clueless about usability! It would have been far easier to supply a built-in or separate utility to automatically collect all the pertinent source files with the option of mailing them to you. It also wouldn't be half as backward if you didn't make me read a

Re: Naming flag for specifying the output file name for Binary Module Interface files

2022-12-14 Thread Iain Sandoe
> On 15 Dec 2022, at 05:58, chuanqi.xcq wrote: > > Hi Nathan, > > > But how do they specify the mapping from module/header-unit name to CMI, so > > that > > imports work? > > > > Is this really a clang-specific mechanism, as it has no module mapper ATM > > (IIUC)? > > Yes, clang doesn't h