Re: Default defs question

2020-07-15 Thread Richard Biener via Gcc
On July 16, 2020 7:09:21 AM GMT+02:00, Gary Oblock via Gcc wrote: >Regarding the other question I asked today could somebody explain to >me what the default_defs are all about. Default defs are SSA names without an explicit defining statement for example those representing values at function e

Default defs question

2020-07-15 Thread Gary Oblock via Gcc
Regarding the other question I asked today could somebody explain to me what the default_defs are all about. I suspect I'm doing something wrong with regard of them. Note, I've isolated the failure in the last email down to this bit (in red): if (is_empty (*entry) || (!is_deleted (*entry) &&

Re: documentation of powerpc64{,le}-linux-gnu as primary platform

2020-07-15 Thread Segher Boessenkool
On Thu, Jul 09, 2020 at 08:18:56PM -0500, Bill Schmidt via Gcc wrote: > >>>No, I don't leave this alone. The little endian target is dropped in > >>GCC 9 and > >>>GCC 10. Is this really what you intended to do? > >>No, it's not dropped. Some people are being pedantic about the name, > >>which is

Help on a bug showing up in a template

2020-07-15 Thread Gary Oblock via Gcc
I'm encountering a really painful error. The stack trace is below. The code in hash-table.h is a template and it is really hyper-allergic to instrumentation (a couple of fprintfs caused malloc to have an internal error!) Last time I checked gbd didn't exactly play nice with templates either. Note

Re: GCC 10.2 Release Candidate available from gcc.gnu.org

2020-07-15 Thread William Seurer via Gcc
I tested the release candidate on powerpc64 power 7 BE, power 8 BE, power 8 LE, and power 9 LE and everything looked OK. On 7/15/20 6:50 AM, Richard Biener wrote: The first release candidate for GCC 10.2 is available from https://gcc.gnu.org/pub/gcc/snapshots/10.2.0-RC-20200715/ ftp

Re: Re: Question about function body and function specialization

2020-07-15 Thread Erick Ochoa
On 15.07.20 05:03, Martin Jambor wrote: Hi, On Tue, Jul 14 2020, Erick Ochoa wrote: On 14/07/2020 12:37, Erick Ochoa wrote: Hello, I have a function foo defined on a source file. Sometimes, a function pointer pointing to foo is passed as a parameter to other functions where foo is called i

Re: New x86-64 micro-architecture levels

2020-07-15 Thread Florian Weimer via Gcc
* Mark Wielaard: > One thing that wasn't clear to me from this proposal is how the glibc > dynamic loader checks for the CPU feature flags. This is important for > valgrind since it can communicate those through different means. cpuid > interception, auxv AT_HWCAP/AT_HWCAP2 interception (but not A

Re: Question about function body and function specialization

2020-07-15 Thread Martin Jambor
Hi, On Wed, Jul 15 2020, Erick Ochoa wrote: > Hi, > > I narrowed down that ipa-inline is marking these indirect functions as > unreachable (these functions have been specialized and therefore should > now be direct functions). Therefore, symtab_remove_unreachable_nodes is > called on them. Runn

Re: New x86-64 micro-architecture levels

2020-07-15 Thread H.J. Lu via Gcc
On Wed, Jul 15, 2020 at 7:38 AM Mark Wielaard wrote: > > Hi Florian, > > I understand you want to discuss the x86_64 micro-architecture levels > only in this thread, but it would be nice to have a similar discussion > for other architectures. > > One thing that wasn't clear to me from this proposa

Re: Crash at gimple_code(gimple* )

2020-07-15 Thread David Edelsohn via Gcc
On Wed, Jul 15, 2020 at 10:07 AM Shuai Wang via Gcc wrote: > > Hello! > > Thank you very much. I use the following statement to check and I confirm > that it's not SSA_NAME: > > if (TREE_CODE(operand) != SSA_NAME) return; > > But considering the following code snippet: > > _313 = _312 + 2147450880

Re: New x86-64 micro-architecture levels

2020-07-15 Thread Mark Wielaard
Hi Florian, I understand you want to discuss the x86_64 micro-architecture levels only in this thread, but it would be nice to have a similar discussion for other architectures. One thing that wasn't clear to me from this proposal is how the glibc dynamic loader checks for the CPU feature flags.

Re: Crash at gimple_code(gimple* )

2020-07-15 Thread Martin Jambor
Hi, On Wed, Jul 15 2020, Shuai Wang wrote: > Hello! > > Thank you very much. I use the following statement to check and I confirm > that it's not SSA_NAME: > > if (TREE_CODE(operand) != SSA_NAME) return; > > But considering the following code snippet: > > _313 = _312 + 2147450880; > _314 = (signed

Re: Question about function body and function specialization

2020-07-15 Thread Erick Ochoa
Hi, I narrowed down that ipa-inline is marking these indirect functions as unreachable (these functions have been specialized and therefore should now be direct functions). Therefore, symtab_remove_unreachable_nodes is called on them. Running the following (immediately after materialization):

Re: Crash at gimple_code(gimple* )

2020-07-15 Thread Shuai Wang via Gcc
Hello! Thank you very much. I use the following statement to check and I confirm that it's not SSA_NAME: if (TREE_CODE(operand) != SSA_NAME) return; But considering the following code snippet: _313 = _312 + 2147450880; _314 = (signed char *) _313; _315 = **_314*; // _314

Re: How to refine autovectorized loop

2020-07-15 Thread Andrew Stubbs
On 15/07/2020 03:39, 夏 晋 via Gcc wrote: Hi everyone, I'm trying to autovectorize the loop, and Thank you for the omnipotent macros, everything goes alright. But recently I need to further optimize the loop, I had some problems. As our vector instruction can process 16 numbers at the same

Re: Question about function body and function specialization

2020-07-15 Thread Martin Jambor
Hi, On Tue, Jul 14 2020, Erick Ochoa wrote: > On 14/07/2020 12:37, Erick Ochoa wrote: >> Hello, >> >> I have a function foo defined on a source file. Sometimes, a function >> pointer pointing to foo is passed as a parameter to other functions >> where foo is called indirectly. This indirect cal

GCC 10.2 Release Candidate available from gcc.gnu.org

2020-07-15 Thread Richard Biener
The first release candidate for GCC 10.2 is available from https://gcc.gnu.org/pub/gcc/snapshots/10.2.0-RC-20200715/ ftp://gcc.gnu.org/pub/gcc/snapshots/10.2.0-RC-20200715/ and shortly its mirrors. It has been generated from git commit 932e9140d3268cf2033c1c3e93219541c53fcd29. I have so

GCC 10.1.1 Status Report (2020-07-15)

2020-07-15 Thread Richard Biener
Status == The GCC 10 branch is now frozen for the GCC 10.2 release, all changes to he branch require a RM approval. Quality Data Priority # Change from last report --- --- P1 P2 218 + 2 P3

Re: Crash at gimple_code(gimple* )

2020-07-15 Thread Martin Jambor
Hi, On Wed, Jul 15 2020, Shuai Wang via Gcc wrote: > Hello, > > I am using the following code to iterate different gimple statements: > > ... > gimple* stmt = gsi_stmt(gsi); > if (gimple_assign_load_p(stmt)) { > tree rhs = gimple_assign_rhs1 (stmt); > if (!rhs) return; > gimple* d

Re: Crash at gimple_code(gimple* )

2020-07-15 Thread Richard Biener via Gcc
On Wed, Jul 15, 2020 at 9:30 AM Shuai Wang via Gcc wrote: > > Hello, > > I am using the following code to iterate different gimple statements: > > ... > gimple* stmt = gsi_stmt(gsi); > if (gimple_assign_load_p(stmt)) { > tree rhs = gimple_assign_rhs1 (stmt); > if (!rhs) return; >

Re: GCC Plugin to insert new expressions/statements in the code

2020-07-15 Thread Richard Biener via Gcc
On Tue, Jul 14, 2020 at 11:23 PM Masoud Gholami wrote: > > Hi, > > I am writing a plugin that uses the PLUGIN_PRAGMAS event to register a > custom pragma that is expected to be before a function call as follows: > > int main() { > > char *filename = “path/to/file”; > #pragma inje

Crash at gimple_code(gimple* )

2020-07-15 Thread Shuai Wang via Gcc
Hello, I am using the following code to iterate different gimple statements: ... gimple* stmt = gsi_stmt(gsi); if (gimple_assign_load_p(stmt)) { tree rhs = gimple_assign_rhs1 (stmt); if (!rhs) return; gimple* def_stmt = SSA_NAME_DEF_STMT(rhs); if (!def_stmt) return; s