Re: How to detect user uses -masm=intel?

2021-07-28 Thread Hongtao Liu via Gcc
On Thu, Jul 29, 2021 at 10:49 AM unlvsur unlvsur via Gcc wrote: > > What I mean is that what macro GCC sets when it compiles -masm=intel > > > Int main() > { > #ifdef /*__INTEL_ASM*/ > printf(“intel”); > #else > printf(“at&t”); > #endif > } not fully understand

RE: How to detect user uses -masm=intel?

2021-07-28 Thread unlvsur unlvsur via Gcc
What I mean is that what macro GCC sets when it compiles -masm=intel Int main() { #ifdef /*__INTEL_ASM*/ printf(“intel”); #else printf(“at&t”); #endif } Sent from Mail for Windows 10 From: Andrew Pinski

RE: How to detect user uses -masm=intel?

2021-07-28 Thread unlvsur unlvsur via Gcc
Do not quite understand. Can you show me an example?? Sent from Mail for Windows 10 From: Andrew Pinski Sent: Wednesday, July 28, 2021 21:43 To: unlvsur unlvsur Cc: gcc@gcc.gnu.org

Re: How to detect user uses -masm=intel?

2021-07-28 Thread Andrew Pinski via Gcc
On Wed, Jul 28, 2021 at 6:41 PM unlvsur unlvsur via Gcc wrote: > > Any GCC macro that can tell the code it is using the intel format’s assembly > instead of at&t?? Inside the inline-asm you can use the alternative. Like this: cmp{b}\t{%1, %h0|%h0, %1} This is how GCC implements this inside too.

How to detect user uses -masm=intel?

2021-07-28 Thread unlvsur unlvsur via Gcc
Any GCC macro that can tell the code it is using the intel format’s assembly instead of at&t?? Sent from Mail for Windows 10

Re: A value number issue

2021-07-28 Thread Gary Oblock via Gcc
Richard, Here is more on the actual failure. >From the pre pass dump: : Inserted _975 = (struct node.reorg.reorder *) dedangled_865; Replaced bea_43->tail with _975 in dedangled_864 = bea_43->tail; EMERGENCY DUMP: void master.constprop () { : unsigned long _974; struct node.reorg.reord

[RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (July 29, 2021)

2021-07-28 Thread 吴伟
Hi all, There is an agenda for tomorrow's meeting. If you have topics to discuss or share, please let me know and I can add them to the agenda. Agenda: 1. Discuss the Vector Calling Convention. 2. Status update of implementation for unratified extensions. 3. Open Discussion 4. (optional) Status

Re: daily report on extending static analyzer project [GSoC]

2021-07-28 Thread Ankur Saini via Gcc
AIM For Today: - Make the anlalyzer evaluate the vfunc calls by creating enodes and eedges representing the call. - Make the analyzer not treat such calls as call to "unknown function" --- PROGRESS : - After the analyzer sucessfully found which funcitons to call ( thanks to functions fr

Re: GCC 11.2 Released

2021-07-28 Thread Geoffrey S. Knauth
Thank you! On Wed, Jul 28, 2021, at 03:40, Richard Biener wrote: > The GNU Compiler Collection version 11.2 has been released. > > GCC 11.2 is a bug-fix release from the GCC 11 branch containing important > fixes for regressions and serious bugs in GCC 11.1 with more than 95 bugs > fixed since th

Re: A value number issue

2021-07-28 Thread Richard Biener via Gcc
On Fri, Jul 23, 2021 at 3:40 AM Gary Oblock wrote: > > Richard, > > OK, all that I've gotten so far out of the dump file is > that the name of "_920" is just something sccvn concocted > and wasn't something I accidentally caused. > > That still leaves me with the question of what is going on. > >

Re: tree decl stored during LGEN does not map to a symtab_node during WPA

2021-07-28 Thread Richard Biener via Gcc
On Thu, Jul 22, 2021 at 4:33 PM Erick Ochoa wrote: > > > > > But the addresses are at LGEN time? > > The following is what runs at WPA time > > unsigned long pid = streamer_read_uhwi (&ib); > unsigned long id = streamer_read_uhwi (&ib); > lto_symtab_encoder_t encoder = file_data->symtab_node_encod

GCC 11.2 Released

2021-07-28 Thread Richard Biener
The GNU Compiler Collection version 11.2 has been released. GCC 11.2 is a bug-fix release from the GCC 11 branch containing important fixes for regressions and serious bugs in GCC 11.1 with more than 95 bugs fixed since the previous release. This release is available from the WWW and FTP servers

GCC 11.2.1 Status Report (2021-07-28)

2021-07-28 Thread Richard Biener
Status == The GCC 11.2.0 tarballs have been generated and uploaded and the GCC 11 branch is again open for regression and documentation fixes. Quality Data Priority # Change from last report --- --- P1 P2