https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82337
--- Comment #10 from Ivo Raisr ---
(In reply to Bill Schmidt from comment #9)
I confirm this fixes the problem also in the original full-blown source.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66601
Eric Gallager changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65461
Eric Gallager changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65041
Eric Gallager changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
On Wed, 27 Sep 2017, Michael Meissner wrote:
> The glibc team has requested we define the standard macro (__FP_FAST_FMAF128)
> for PowerPC code when we have the IEEE 128-bit floating point hardware
> instructions enabled.
It's not a standard macro. TS 18661-3 has FP_FAST_FMAF128 as an optional
On Wed, Sep 27, 2017 at 6:58 PM, Richard Sandiford
wrote:
> David Edelsohn writes:
>> On Fri, Sep 15, 2017 at 2:53 AM, Richard Biener wrote:
>>> On Thu, 14 Sep 2017, David Edelsohn wrote:
>>>
* tree-ssa-sccvn.c
On Fri, 2017-09-22 at 11:21 +0200, Bartosz Szreder wrote:
> Hello David,
>
> > > 1. The documentation doesn't mention existence of
> > > gcc_jit_context_new_function_ptr_type() as a mechanism of
> > > handling
> > > function pointers, yet contains
> > > gcc_jit_context_new_call_through_ptr().
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71727
--- Comment #4 from Christophe Lyon ---
Author: clyon
Date: Wed Sep 27 23:52:58 2017
New Revision: 253242
URL: https://gcc.gnu.org/viewcvs?rev=253242=gcc=rev
Log:
[AArch64] PR71727 fix -mstrict-align
2017-09-27 Christophe Lyon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82347
Bug ID: 82347
Summary: Class Name Injection and Constructor Typenames
Product: gcc
Version: 7.0.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
On 09/27/2017 08:54 PM, Liu Hao wrote:
> On 2017/9/28 4:09, Joseph Myers wrote:
>> On Thu, 28 Sep 2017, Liu Hao wrote:
>>
>>> Colorized diagnostics used to be disabled for MinGW targets (on which
>>> the macro `_WIN32` is defined), and this patch enables it.
>>
>> I'd hope this is all to do with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82343
Mark changed:
What|Removed |Added
Attachment #42244|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82172
--- Comment #21 from Gubbins ---
(In reply to Martin Liška from comment #20)
> Your failure happens even w/o LTO, am I right?
> But yes, the problem looks very similar to what happens for ld.bfd.
You are right.
Does anyone know how I would
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81509
--- Comment #6 from Steve Kargl ---
On Wed, Sep 27, 2017 at 10:59:56PM +, dominiq at lps dot ens.fr wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81509
>
> --- Comment #5 from Dominique d'Humieres ---
> pr45513 and pr54072 could be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80210
--- Comment #16 from Peter Bergner ---
While investigating the new failure in Comment 15, I modified the test case
slightly to move the #pragma to the beginning of the test case. I found I get
another similar looking ICE, but which isn't the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82346
--- Comment #7 from Jonathan Wakely ---
The condition for std::to_string being declared in gcc-5 is:
#if __cplusplus >= 201103L && defined(_GLIBCXX_USE_C99)
So presumably _GLIBCXX_USE_C99 is false. If you're using glibc 2.26 you might
have hit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80210
Peter Bergner changed:
What|Removed |Added
Status|CLOSED |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81509
--- Comment #5 from Dominique d'Humieres ---
pr45513 and pr54072 could be duplicates.
David Edelsohn writes:
> On Fri, Sep 15, 2017 at 2:53 AM, Richard Biener wrote:
>> On Thu, 14 Sep 2017, David Edelsohn wrote:
>>
>>> * tree-ssa-sccvn.c (visit_phi): Merge undefined values similar
>>> to VN_TOP.
>>>
>>> This seems to have regressed
>>>
>>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82346
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
Snapshot gcc-6-20170927 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/6-20170927/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6
The glibc team has requested we define the standard macro (__FP_FAST_FMAF128)
for PowerPC code when we have the IEEE 128-bit floating point hardware
instructions enabled.
This patch does this in the PowerPC backend. As I look at the whole issue, at
some point we should do this more in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82338
--- Comment #1 from David Binderman ---
12 hours reducing leads to this C++ code:
extern "C" {
void a();
void *memset(void *, int, unsigned long);
}
struct b {
int c;
int d;
} e[5000], *f;
int g;
int h;
int i;
int j, k;
void l(int);
int m;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82302
--- Comment #9 from krzysio.kurek at wp dot pl ---
I think I located the issue, it works fine on my machine, but using I found an
error using glslangValidator.
Please try pulling and compiling again.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68924
--- Comment #3 from Peter Cordes ---
(In reply to Marc Glisse from comment #2)
> Does anything bad happen if you remove the #ifdef/#endif for
> _mm_cvtsi64_si128? (2 files in the testsuite would need updating for a
> proper patch)
It's just a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82346
--- Comment #5 from krzysio.kurek at wp dot pl ---
$ g++-5 -std=c++11 main.cpp -o string -v
Using built-in specs.
COLLECT_GCC=g++-5
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper
Target: x86_64-linux-gnu
Configured with:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82346
Andrew Pinski changed:
What|Removed |Added
Component|c++ |libstdc++
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82346
--- Comment #4 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #3)
> Can you provide the exact output of g++ then?
Can you provide the exact output of g++ -v then?
Sorry for the typo.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82346
krzysio.kurek at wp dot pl changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Greetings All,
I commented here a few names ago,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82230. Not
to be a annoyance but I have a school assignment and would like someone to
reply if it's
correct or something. I am assuming it's probably wrong but any comment would
be very
helpful
On 2017/9/28 4:09, Joseph Myers wrote:
On Thu, 28 Sep 2017, Liu Hao wrote:
Colorized diagnostics used to be disabled for MinGW targets (on which
the macro `_WIN32` is defined), and this patch enables it.
I'd hope this is all to do with MinGW host, and nothing to do with the
target.
Oh you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82346
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82346
Bug ID: 82346
Summary: String is not detected as a part of std
Product: gcc
Version: 5.4.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Hi
I would like to propose to add a new dg-require-normal-namespace
attribute to make several tests failing when version namespace is active
UNSUPPORTED. It is like dg-require-normal-mode but also consider when
version namespace is being used.
I still need to complete execution of
Ping.
Steve Ellcey
sell...@cavium.com
On Thu, 2017-08-31 at 10:24 -0700, Steve Ellcey wrote:
> On Tue, 2017-08-29 at 12:25 +0100, Szabolcs Nagy wrote:
> >
> >
> > in glibc the hwcap is not used, because it has accesses to
> > cached dispatch info, but in libatomic using the hwcap
> > argument
Hi
I just committed attached patch as trivial.
Those tests were highly istreambuf_iterator implementation, it is
the result of the call to money_get<>::get which is pointing immediately
beyond the last character recognized to quote Standard words.
2017-09-27 François Dumont
On Thu, 28 Sep 2017, Liu Hao wrote:
> Colorized diagnostics used to be disabled for MinGW targets (on which
> the macro `_WIN32` is defined), and this patch enables it.
I'd hope this is all to do with MinGW host, and nothing to do with the
target.
--
Joseph S. Myers
jos...@codesourcery.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82339
--- Comment #5 from Peter Cordes ---
(In reply to Richard Biener from comment #2)
> I always wondered if it is more efficient to have constant pools per function
> in .text so we can do %rip relative loads with short displacement?
There's no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66756
--- Comment #12 from Thomas Koenig ---
Correction... the patch does not work with a simple
example such as
program main
!$OMP PARALLEL NUM_THREADS(4)
print *,"Hello, world"
!$OMP END PARALLEL
end program main
Some more digging to do...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81509
--- Comment #4 from kargl at gcc dot gnu.org ---
A patch has been submitted. See
https://gcc.gnu.org/ml/fortran/2017-09/msg00124.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82337
--- Comment #9 from Bill Schmidt ---
Revised and tested patch posted here:
https://gcc.gnu.org/ml/gcc-patches/2017-09/msg01836.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82324
janus at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
The attached patch fixes PR fortran/81509.
In short, F2008 now allows boz-literal-constants in IAND, IOR, IEOR,
DSHIFTL, DSHIFTR, and MERGE_BITS. gfortran currently allows BOZ
argument, but she was not enforcing restrictions in F2008. The
attach patch causes gfortran to conform to F2008.
As
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66756
--- Comment #11 from Thomas Koenig ---
Created attachment 42250
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42250=edit
Proposed patch
This patch is an attempt at getting rid of the lock-order
inversion. It seems to do the right thing,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82339
--- Comment #4 from Peter Cordes ---
(In reply to Jakub Jelinek from comment #0)
> At least on i7-5960X in the following testcase:
>
> baz is fastest as well as shortest.
> So I think we should consider using movl $cst, %edx; shlq $shift, %rdx
Hi,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82337 reports a problem
with SLSR performing an invalid optimization across an abnormal PHI.
This is easy to avoid by ensuring that SSA names used in an abnormal
PHI never appear as a basis or as a PHI basis in the candidate table.
We won't
On Wed, Sep 27, 2017 at 06:25:56PM +0100, Christophe Lyon wrote:
> ping?
OK, thanks.
Reviewed-by: James Greenhalgh
James
>
> On 20 September 2017 at 15:17, Christophe Lyon
> wrote:
> > Hi,
> >
> > On 11 September 2017 at 10:45, Andrew
Hello,
(I don't have SVN write access. So please apply this patch if you think
it is OK. I have got FSF's copyright assignment paper for GCC. I will
send you a copy of it when required.)
Colorized diagnostics used to be disabled for MinGW targets (on which
the macro `_WIN32` is defined), and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69493
Peter Bergner changed:
What|Removed |Added
CC||bergner at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82258
--- Comment #9 from Christophe Lyon ---
I get:
1 2 1 0 -2 -3
-4
3 4 5 0 7 8
9
Hi James
I have made the requested changes to the patch.
2017-09-27 Sudakshina Das
* config/aarch64/aarch64-protos.h (enum simd_immediate_check): New
check type
for aarch64_simd_valid_immediate.
(aarch64_output_simd_mov_immediate): Update
The following patch corrects some Power9 resource requirements and
instruction latencies. Bootstrap/regtest on powerpc64le-linux with no
new regressions. Ok for trunk?
-Pat
2017-09-27 Pat Haugen
* config/rs6000/power9.md (DU_C2_3_power9): Remove an incorrect
This patch by Than McIntosh fixes a crash in the Go frontend that
incorrectly embeds a pointer type. This fixes
https://golang.org/issue/22050. Bootstrapped and ran Go testsuite on
x86_64-pc-linux-gnu. Committed to mainline.
Ian
Index: gcc/go/gofrontend/MERGE
On 09/27/2017 03:05 AM, Rainer Orth wrote:
Hi Andreas,
On 09/27/2017 10:10 AM, Rainer Orth wrote:
Hi Andreas,
On 09/26/2017 02:26 PM, Rainer Orth wrote:
Hi Andreas,
diff --git a/gcc/doc/sourcebuild.texi b/gcc/doc/sourcebuild.texi
index 307c726..3acfd85 100644
---
ping?
On 20 September 2017 at 15:17, Christophe Lyon
wrote:
> Hi,
>
> On 11 September 2017 at 10:45, Andrew Pinski wrote:
>> On Tue, Jul 18, 2017 at 5:50 AM, Christophe Lyon
>> wrote:
>>> Hello,
>>>
>>> I've received a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82345
Jonathan Wakely changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #5 from Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82345
--- Comment #4 from Jonathan Wakely ---
When I compare the performance of this similar program on a text file of 4
million lines I see gcc performs slightly better:
#include
#include
#include
int main(int , char**argv) {
std::ifstream
On Wed, 27 Sep 2017, Florian Weimer wrote:
> This is part of the ABI GCC implements, so it has to be documented somewhere,
> and not just as part of the GCC source code.
>
> CET is not properly described in the ABI supplement and I don't think this
> will change, so detailed documentation in the
On 09/27/2017 02:52 AM, Florian Weimer wrote:
On 09/27/2017 05:40 AM, Sandra Loosemore wrote:
+@emph{x86 implementation:} when @option{-fcf-protection} option is
+specified the compiler inserts an ENDBR instruction at function's
+prologue if the function's type does not have the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82345
--- Comment #3 from Eugene ---
Created attachment 42249
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42249=edit
source code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82345
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82345
--- Comment #1 from Eugene ---
Source file https://yadi.sk/d/FqXH-4Y63NGeSw
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82345
Bug ID: 82345
Summary: low performance (comparing to clang)
Product: gcc
Version: 7.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63392
Eric Gallager changed:
What|Removed |Added
Keywords||error-recovery
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82341
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
Hi Nathan,
This patch is a tweak for the C++ part of the type safety
enhancement to attribute ifunc committed in r253041. It touches
the C++ ifunc tests you added some years ago and I recently broke
with the initial commits of the feature. The notable difference
between r253041 and this update
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82337
--- Comment #8 from Bill Schmidt ---
Created attachment 42248
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42248=edit
Proposed patch
Here's what I'm testing -- looks like it fixes this particular case.
Updated version #3.
> -Original Message-
> From: Sandra Loosemore [mailto:san...@codesourcery.com]
> Sent: Wednesday, September 27, 2017 5:41 AM
> To: Tsimbalist, Igor V ; Uros Bizjak
>
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82337
--- Comment #7 from Bill Schmidt ---
I think we can do something simpler by just keeping these abnormal SSA names
out of the basis chains in the table. Working on a patch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82342
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82344
Bug ID: 82344
Summary: [8 Regression] SPEC CPU2006 435.gromacs ~10%
performance regression with trunk@250855
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Jakub,
The following patch implements P0386R1 - NSDMIs for bit-fields.
While working on that, I've discovered our parser mishandles attributes
on bitfields, already C++11 says:
identifier[opt] attribute-specifier-seq[opt] : constant-expression
in the grammar, but we actually parsed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82012
Andreas Krebbel changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Wed, 27 Sep 2017, Richard Biener wrote:
> On Wed, 27 Sep 2017, Richard Biener wrote:
>
> > On Tue, 26 Sep 2017, Sebastian Pop wrote:
> >
> > > On Mon, Sep 25, 2017 at 8:12 AM, Richard Biener wrote:
> > >
> > > > On Fri, 22 Sep 2017, Sebastian Pop wrote:
> > > >
> > > > >
This patch by Tony Reix checks for errors from Getsockname in a couple
of places. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu.
Committed to mainline.
Ian
Index: gcc/go/gofrontend/MERGE
===
--- gcc/go/gofrontend/MERGE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68924
--- Comment #2 from Marc Glisse ---
Does anything bad happen if you remove the #ifdef/#endif for _mm_cvtsi64_si128?
(2 files in the testsuite would need updating for a proper patch)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82159
--- Comment #4 from Jakub Jelinek ---
Author: jakub
Date: Wed Sep 27 14:19:57 2017
New Revision: 253230
URL: https://gcc.gnu.org/viewcvs?rev=253230=gcc=rev
Log:
PR c++/82159
* gimplify.c (gimplify_modify_expr): Don't optimize
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82340
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
Hi!
On Mon, 25 Sep 2017 16:57:52 +0200, Tom de Vries wrote:
> currently for a GOACC_REDUCTION internal fn call we print:
> ...
>sum_5 = GOACC_REDUCTION (SETUP, _3, 0, 0, 67, 0);
> ...
>
> This patch adds a comment for some arguments explaining the meaning of
> the
Hi!
Doing a movl + shlq by constant seems to be 1 byte shorter
than movabsq, so this patch attempts to use the former form
unless flags is live.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
Performance-wise, not really sure what is a win (on i7-5960X on the
testcase in
On Wed, 27 Sep 2017, Jakub Jelinek wrote:
> Hi!
>
> The expansion relies on lhs being kept for calls that return addressable
> types. On the following testcase (which is a GNU extension, pedantically
> we error out on zero sized arrays) we return TREE_ADDRESSABLE
> zero_sized_type and optimize
Hi!
The expansion relies on lhs being kept for calls that return addressable
types. On the following testcase (which is a GNU extension, pedantically
we error out on zero sized arrays) we return TREE_ADDRESSABLE
zero_sized_type and optimize away the lhs which we need later on.
Fixed thusly,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82339
Alexander Monakov changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81398
d25fe0be@ changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82337
Bill Schmidt changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |wschmidt at gcc dot
gnu.org
---
On Wed, 27 Sep 2017, Richard Biener wrote:
> On Tue, 26 Sep 2017, Sebastian Pop wrote:
>
> > On Mon, Sep 25, 2017 at 8:12 AM, Richard Biener wrote:
> >
> > > On Fri, 22 Sep 2017, Sebastian Pop wrote:
> > >
> > > > On Fri, Sep 22, 2017 at 8:03 AM, Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82343
Bug ID: 82343
Summary: internal compiler error: Segmentation fault - template
recurrency, SFINAE
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82341
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |8.0
--- Comment #1 from Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82342
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |8.0
--- Comment #1 from Richard Biener
Hi,
this patch makes the test-case
libgomp.oacc-c-c++-common/parallel-reduction.c work for non-nvidia devices.
Committed as obvious.
Thanks,
- Tom
Fix libgomp.oacc-c-c++-common/parallel-reduction.c for non-nvidia devices
2017-09-27 Tom de Vries
*
Updated version #4.
> -Original Message-
> From: Sandra Loosemore [mailto:san...@codesourcery.com]
> Sent: Wednesday, September 27, 2017 5:11 AM
> To: Tsimbalist, Igor V ; 'gcc-
> patc...@gcc.gnu.org'
> Cc: Jeff Law
Currently ISL aborts on this special value and for debugging (and
tuning?) it's nice to avoid all the clutter introduced by tiling.
Committed as obvious.
Richard.
2017-09-27 Richard Biener
* graphite-optimize-isl.c (get_schedule_for_node_st): Allow
On Tue, 26 Sep 2017, Sebastian Pop wrote:
> On Mon, Sep 25, 2017 at 8:12 AM, Richard Biener wrote:
>
> > On Fri, 22 Sep 2017, Sebastian Pop wrote:
> >
> > > On Fri, Sep 22, 2017 at 8:03 AM, Richard Biener
> > wrote:
> > >
> > > >
> > > > This simplifies
> -Original Message-
> From: Florian Weimer [mailto:fwei...@redhat.com]
> Sent: Wednesday, September 27, 2017 10:52 AM
> To: Sandra Loosemore ; Tsimbalist, Igor V
> ; Uros Bizjak
> Cc: gcc-patches@gcc.gnu.org
>
The following is to allow making --param graphite-max-arrays-per-scop
unbounded. That's a little tricky because the bound is used when
computing "alias-sets" for scalar constraints. There's an easy way
out though as we know the maximum alias-set assigned in the SCOP,
we only have to remember
Turns out loop_nest recorded in scop-info isn't really necessary as
we can simply process parameters in loop bounds during the gather_bbs
walk where we encounter each loop (identified by its header) once.
This avoids the linear search in record_loop_in_sese.
Bootstrap / regtest running on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82095
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82115
Jakub Jelinek changed:
What|Removed |Added
CC||jason at gcc dot gnu.org,
This removes another quadraticness from SCOP detection, gather_bbs
domwalk. This is done by enhancing domwalk to handle SEME regions
via a special return value from before_dom_children.
With this I'm now confident to remove the
PARAM_GRAPHITE_MAX_BBS_PER_FUNCTION parameter and its associated
On 18/09/17 17:39, Richard Sandiford wrote:
> ALL_REGS doesn't function as a union class of POINTER_REGS and FP_REGS
> since it includes the CC register as well. REGNO_REG_CLASS (CC_REGNUM)
> is NO_REGS, but of course NO_REGS rightly doesn't include CC_REGNUM.
>
> Adding a union class for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82138
Jakub Jelinek changed:
What|Removed |Added
Priority|P3 |P4
CC|
1 - 100 of 145 matches
Mail list logo