On 07/24/2018 05:18 PM, Bernd Edlinger wrote:
> On 07/24/18 23:46, Jeff Law wrote:
>> I'd like to ask we hold on this until I return from PTO (Aug 1) so that
>> we can discuss the best thing to do here for each class of change.
>>
>
> Okay.
>
>> I think you, Martin, Richi and myself should hash
On 07/24/2018 06:17 PM, Sandra Loosemore wrote:
> On 07/24/2018 03:24 PM, Jeff Law wrote:
>>>
Any thoughts on using the newer function descriptor bits rather than
old
style stack trampolines?
>>>
>>> Has that been committed? I vaguely remembered discussion of a new way
>>> to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86668
Bug ID: 86668
Summary: mixing ansi prototype with K definition
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37200
Eric Gallager changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26613
--- Comment #8 from Andrew Pinski ---
(In reply to Eric Gallager from comment #7)
> (In reply to Mark F. Haigh from comment #5)
> > Created attachment 11005 [details]
> > Fix for trunk (against 2006-03-03 CVS)
>
> Could you submit a newer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86631
Martin Sebor changed:
What|Removed |Added
Keywords||patch
--- Comment #4 from Martin Sebor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=8
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86532
Martin Sebor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86667
--- Comment #2 from Andrew Pinski ---
*** Bug 8 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86622
--- Comment #8 from Martin Sebor ---
Author: msebor
Date: Wed Jul 25 02:11:31 2018
New Revision: 262958
URL: https://gcc.gnu.org/viewcvs?rev=262958=gcc=rev
Log:
PR tree-optimization/86622 - incorrect strlen of array of array plus variable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83819
Bug 83819 depends on bug 86622, which changed state.
Bug 86622 Summary: [9 Regression] incorrect strlen of array of array plus
variable offset
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86622
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86622
Martin Sebor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86532
--- Comment #29 from Martin Sebor ---
Author: msebor
Date: Wed Jul 25 02:11:31 2018
New Revision: 262958
URL: https://gcc.gnu.org/viewcvs?rev=262958=gcc=rev
Log:
PR tree-optimization/86622 - incorrect strlen of array of array plus variable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86471
--- Comment #26 from Matt Bentley ---
(In reply to Jonathan Wakely from comment #25)
> What warning? Why can't you just pass 0 to __builtin_memset? It's a null
> pointer constant. I don't see any warning from clang when using -Weverything.
As
The very large option argument enhancement committed last week
inadvertently introduced an assumption about the LP64 data model
that makes the -Wxxx-larger-than options have a different effect
at their default documented setting of PTRDIFF_MAX between ILP32
and LP64. As a result, the options are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86667
--- Comment #1 from urbanjost at comcast dot net ---
Created attachment 44434
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44434=edit
C code for interfacing to Fortran for printing environment table
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86667
Bug ID: 86667
Summary: can no longer traverse environment table
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=8
Bug ID: 8
Summary: Can no longer traverse and read process environment
table
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
On 07/24/2018 03:24 PM, Jeff Law wrote:
Any thoughts on using the newer function descriptor bits rather than old
style stack trampolines?
Has that been committed? I vaguely remembered discussion of a new way
to handle nested functions without using the trampoline interface, but I
couldn't
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86665
Bug ID: 86665
Summary: declaration conflicts with target of using declaration
already in scope
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
On 07/24/18 23:46, Jeff Law wrote:
> On 07/24/2018 01:59 AM, Bernd Edlinger wrote:
>> Hi!
>>
>> This patch makes strlen range computations more conservative.
>>
>> Firstly if there is a visible type cast from type A to B before passing
>> then value to strlen, don't expect the type layout of B to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86664
--- Comment #1 from Alexander Kondratskiy ---
Calling c++filt on the symbol (see attachment) results in a segfault.
This may be a similar issue to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82890
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86664
Bug ID: 86664
Summary: Demangler segfaults
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: demangler
cc/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc/configure --prefix=/home/absozero/trunk/root-gcc
--enable-languages=c,c++ --disable-werror --enable-multilib
Thread model: posix
gcc version 9.0.0 20180724 (experimental) [trunk revision 262942] (G
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86662
--- Comment #1 from Jozef Lawrynowicz ---
Untested patch
diff --git a/gcc/tree.c b/gcc/tree.c
index bace9c8..54384ad 100644
--- a/gcc/tree.c
+++ b/gcc/tree.c
@@ -9802,8 +9802,7 @@ build_common_tree_nodes (bool signed_char)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86662
Bug ID: 86662
Summary: msp430-elf segfault with -flto and -mlarge
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86631
--- Comment #3 from joseph at codesourcery dot com ---
The relevant point is after do_compile calls lang_dependent_init. Since
PTRDIFF_TYPE is a string, it's a pain to do anything with it until after
the front end has set up tree nodes
-languages=c,c++ --disable-werror --enable-multilib
Thread model: posix
gcc version 9.0.0 20180724 (experimental) [trunk revision 262942] (GCC)
$ g++-trunk abc.C
abc.C:5:31: internal compiler error: tree check: expected tree that contains
‘decl minimal’ structure, have ‘overload
On 07/24/2018 02:16 PM, Martin Sebor wrote:
> On 07/20/2018 04:20 AM, Richard Biener wrote:
>> On Thu, 19 Jul 2018, Martin Sebor wrote:
>>
>>> Here's one more update with tweaks addressing a couple more
>>> of Bernd's comments:
>>>
>>> 1) correct the use of TREE_STRING_LENGTH() where a number of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86599
--- Comment #5 from The Written Word
---
(In reply to The Written Word from comment #4)
> On HP-UX 11.23/PA, this isn't an issue because of the following in
> fixincludes/inclhack.def:
> /*
> * HP-UX long_double
> */
> fix = {
> hackname
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86660
--- Comment #1 from cesar at gcc dot gnu.org ---
Created attachment 44431
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44431=edit
LTO graceful abort patch
With the LTO graceful abort patch, I now see this error:
lto1: error: Missing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86599
The Written Word changed:
What|Removed |Added
Version|7.2.0 |8.1.0
--- Comment #4 from The
On Tue, 2018-07-24 at 22:04 +0100, James Greenhalgh wrote:
>
>
> I'd say this patch isn't desirable for trunk. I'd be interested in use cases
> that need a static decision on presence of LSE that are not better expressed
> using higher level language features.
>
> Thanks,
> James
How about
On 07/24/2018 06:18 AM, Martin Liška wrote:
> Hi.
>
> That's simple patch that improves documentation as requested
> in the PR.
>
> Ready for trunk?
> Martin
>
> gcc/ChangeLog:
>
> 2018-07-24 Martin Liska
>
> PR sanitizer/79635
> * params.def: Explain ASan abbreviation and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86660
Bug ID: 86660
Summary: libgomp.c++/for-15.C ICEs with nvptx offloading
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
On 07/24/2018 01:59 AM, Bernd Edlinger wrote:
> Hi!
>
> This patch makes strlen range computations more conservative.
>
> Firstly if there is a visible type cast from type A to B before passing
> then value to strlen, don't expect the type layout of B to restrict the
> possible return value
On 07/23/2018 08:33 AM, Richard Earnshaw (lists) wrote:
> [sorry, missed this mail somehow]
>
> On 11/07/18 22:01, Jeff Law wrote:
>> On 07/09/2018 10:38 AM, Richard Earnshaw wrote:
>>> This patch is the main part of the speculation tracking code. It adds
>>> a new target-specific pass that is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86599
--- Comment #3 from The Written Word
---
6.4.0 and 7.3.0 exhibit the same error.
On 07/24/2018 12:18 PM, Sandra Loosemore wrote:
> On 07/24/2018 09:45 AM, Jeff Law wrote:
>> On 07/23/2018 10:21 PM, Sandra Loosemore wrote:
>>> 2018-07-23 Jojo
>>> Huibin Wang
>>> Sandra Loosemore
>>> Chung-Lin Tang
>>>
>>> C-SKY port:
On 07/24/2018 11:18 AM, Segher Boessenkool wrote:
> This patch allows combine to combine two insns into two. This helps
> in many cases, by reducing instruction path length, and also allowing
> further combinations to happen. PR85160 is a typical example of code
> that it can improve.
>
> This
This is missing the synchronized_pool_resource and
unsynchronized_pool_resource classes but is otherwise complete.
This is a new implementation, not based on the existing code in
, but memory_resource and
polymorphic_allocator ended up looking almost the same anyway.
The constant_init kluge in
On 07/24/2018 12:11 PM, Richard Sandiford wrote:
> This PR shows a pathological case in which we try SLP vectorisation on
> dead code. We record that 0 bits of the result are enough to satisfy
> all users (which is true), and that led to precision being 0 in:
>
> static unsigned int
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86631
--- Comment #2 from Martin Sebor ---
I just happen to be looking into this. Is there a way to defer the option
processing until after all this info is available? (When things like
ptrdiff_type_node are already initialized, or at least when the
On 07/24/2018 09:06 PM, Alexandre Oliva wrote:
> On Jul 24, 2018, Tom de Vries wrote:
>
>> There's a design principle in GCC that code generation and debug generation
>> are independent. This guarantees that if you're encountering a problem in an
>> application without debug info, you can
On Tue, Jul 24, 2018 at 03:22:02PM -0500, Steve Ellcey wrote:
> This is a patch for PR 86538, to define an __ARM_FEATURE_LSE macro
> when LSE is available. Richard Earnshaw closed PR 86538 as WONTFIX
> because the ACLE (Arm C Language Extension) does not require this
> macro and because he is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86631
--- Comment #1 from joseph at codesourcery dot com ---
On Sun, 22 Jul 2018, msebor at gcc dot gnu.org wrote:
> In ILP32 it sets the limit for the warning to LLONG_MAX which is greater than
> the value of PTRDIFF_MAX on the targer (the intended
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86658
--- Comment #3 from Jonathan Wakely ---
Author: redi
Date: Tue Jul 24 20:49:10 2018
New Revision: 262952
URL: https://gcc.gnu.org/viewcvs?rev=262952=gcc=rev
Log:
PR libstdc++/86658 fix __niter_wrap to not copy invalid iterators
An output
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86658
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
An output iterator passed as the unused first argument to __niter_wrap
might have already been invalidated, so don't copy it.
PR libstdc++/86658
* include/bits/stl_algobase.h (__niter_wrap<_Iterator>): Pass unused
parameter by reference, to avoid copying invalid
From: Tom de Vries
As the title mentions, this patch generalizes the state propagation and
synchronization code. Note that while the patch makes reference to
large_vectors, they are not enabled in nvptx_goacc_validate_dims.
Therefore, only the worker case is exercised in this patch.
2018-XX-YY
From: Cesar Philippidis
Chung-Lin had originally defined TARGET_SET_CURRENT_FUNCTION as part
of his gang-local variable patch. But I intend to introduce those
changes at a later time. Eventually the state propagation code will
utilize nvptx_set_current_function to reset the reduction buffer
From: Tom de Vries
This patch replaces the confusing, in-lined min, max and rounding code
sprinkled throughout the nvptx BE with calls to MIN, MAX, and ROUND_UP
macros.
2018-XX-YY Tom de Vries
Cesar Philippidis
gcc/
* config/nvptx/nvptx.c
From: Tom de Vries
This patch introduces an axis_dim member to the machine_function
struct. The launch geometry will be queried frequently enough so that
its justified to store that information with each cfun.
2018-XX-YY Tom de Vries
Cesar Philippidis
gcc/
*
From: Cesar Philippidis
This patch teaches nvptx_single to always use barrier '0' for CTA
synchronization. This started off as a cosmetic change, but later on
each large vector (i.e. one that larger than a PTX warp) will need to
use its own unique thread barrier to avoid thread divergence.
From: Tom de Vries
This patch extends the nvptx_barsync pattern to accept an integeral
parameter to specify how many threads utilize the requested
barrier. This is necessary variable length vectors, as each large
vector will require own thread barrier.
2018-XX-YY Tom de Vries
From: Tom de Vries
This patch only adjusts white space.
2018-XX-YY Cesar Philippidis
gcc/
* config/nvptx/nvptx.c (nvptx_single): Fix whitespace.
(nvptx_neuter_pars): Likewise.
(cherry picked from openacc-gcc-7-branch commit
10f697dfcdaa77b842de6e9a62c68b33a49d3c16)
From: Cesar Philippidis
This patch introduces a new struct offload_attrs, which contains the
details regarding the offload function launch geometry. In addition to
its current usage to neuter worker and vector threads, it will
eventually by used to validate the compile-time launch geometry
From: Cesar Philippidis
This patch renames various state propagation functions into somewhat
that reflects their usage in generic worker and vector contexts. E.g.,
whereas before nvptx_wpropagate used to be used exclusively for worker
state propagation, it will eventually be used for any state
From: Cesar Philippidis
Eventually, we want the nvptx BE to use a common shared memory buffer
for both worker and vector state propagation (albeit using different
partitions of shared memory for each logical thread). This patch
renames the worker_bcast variables into a more generic oacc_bcast.
From: Cesar Philippidis
This patch series contains various cleanups and structural
reorganizations to the NVPTX BE in preparation for the forthcoming
variable length vector length enhancements. Tom, in order to make
these changes easier for you to review, I broke these patches into
logical
From: Cesar Philippidis
Besides for updating the macros for the NVPTX OpenACC dims, this patch
also renames PTX_GANG_DEFAULT to PTX_DEFAULT_RUNTIME_DIM. I had
originally included the PTX_GANG_DEFAULT hunk in an earlier libgomp
patch, but going forward it makes sense to isolate the nvptx and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58224
janus at gcc dot gnu.org changed:
What|Removed |Added
Keywords||diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86658
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
This is a patch for PR 86538, to define an __ARM_FEATURE_LSE macro
when LSE is available. Richard Earnshaw closed PR 86538 as WONTFIX
because the ACLE (Arm C Language Extension) does not require this
macro and because he is concerned that it might encourage people to
use inline assembly instead
On 07/24/2018 01:48 PM, Franz Sirl wrote:
Am 2018-07-24 um 17:35 schrieb Martin Sebor:
On 07/24/2018 03:24 AM, Franz Sirl wrote:
Am 2018-07-20 um 23:22 schrieb Martin Sebor:
As the last observation in PR 82063 Jim points out that
Both -Warray-bounds and -Warray-bounds= are listed in the
On 07/20/2018 04:20 AM, Richard Biener wrote:
On Thu, 19 Jul 2018, Martin Sebor wrote:
Here's one more update with tweaks addressing a couple more
of Bernd's comments:
1) correct the use of TREE_STRING_LENGTH() where a number of
array elements is expected and not bytes
2) set CHARTYPE as soon
Am 2018-07-24 um 17:35 schrieb Martin Sebor:
On 07/24/2018 03:24 AM, Franz Sirl wrote:
Am 2018-07-20 um 23:22 schrieb Martin Sebor:
As the last observation in PR 82063 Jim points out that
Both -Warray-bounds and -Warray-bounds= are listed in the c.opt
file as being enabled by -Wall, but
On Tue, Jul 24, 2018 at 12:19:30PM -0600, Sandra Loosemore wrote:
> On 07/24/2018 12:10 PM, Segher Boessenkool wrote:
> >On Mon, Jul 23, 2018 at 10:26:35PM -0600, Sandra Loosemore wrote:
> >>diff --git a/libgcc/config.host b/libgcc/config.host
> >>index 18cabaf..b2ee0c9 100644
> >>---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86598
--- Comment #3 from joseph at codesourcery dot com ---
On Fri, 20 Jul 2018, zhonghao at pku dot org.cn wrote:
> g++ rejects the above code:
You don't say what options you are using, or what compiler version; please
include that in future bug
On 07/24/2018 11:05 AM, David Malcolm wrote:
On Mon, 2018-07-23 at 20:56 -0600, Martin Sebor wrote:
On 07/23/2018 07:20 PM, David Malcolm wrote:
On Mon, 2018-07-23 at 17:49 -0600, Martin Sebor wrote:
(David, I'm hoping your your help here. Please see the end.)
While looking into a recent
Hello, Christina,
On Jul 24, 2018, Tamar Christina wrote:
> gcc/
> 2018-07-24 Tamar Christina
> PR target/86486
> * configure.ac: Add stack-clash-protection-guard-size.
> * doc/install.texi: Document it.
> * config.in (DEFAULT_STK_CLASH_GUARD_SIZE): New.
> *
On Jul 24, 2018, Tom de Vries wrote:
> This patch adds fake uses of user variables at the point where they go out of
> scope, to keep user variables inspectable throughout the application.
I suggest also adding such uses before sets, so that variables aren't
regarded as dead and get optimized
On Jul 24, 2018, Tom de Vries wrote:
> There's a design principle in GCC that code generation and debug generation
> are independent. This guarantees that if you're encountering a problem in an
> application without debug info, you can recompile it with -g and be certain
> that you can
On Jul 19, 2018, Richard Biener wrote:
> Oh, that probably wasn't omitted on purpose. Cary said it was used
> for profiling but I can't see any such use.
> Is the instance discriminator stuff also used for profiling?
Not that I know, but... I probably wouldn't know yet ;-)
Anyway, it was
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86538
--- Comment #2 from Steve Ellcey ---
While I agree that we want users to use the __sync and atomic primitives,
it still seems like it would be useful in some cases to know if the LSE
operations are available and if GCC is generating code for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86659
Rainer Orth changed:
What|Removed |Added
Target Milestone|--- |9.0
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: ebotcazou at gcc dot gnu.org
Target Milestone: ---
Target: sparc-sun-solaris2.*
Between 20180723 (r262933) and 20180724 (r262948) a couple of gnat.dg tests
started to FAIL
On 07/24/2018 12:10 PM, Segher Boessenkool wrote:
On Mon, Jul 23, 2018 at 10:26:35PM -0600, Sandra Loosemore wrote:
diff --git a/libgcc/config.host b/libgcc/config.host
index 18cabaf..b2ee0c9 100644
--- a/libgcc/config.host
+++ b/libgcc/config.host
@@ -94,6 +94,9 @@ am33_2.0-*-linux*)
On 07/24/2018 09:45 AM, Jeff Law wrote:
On 07/23/2018 10:21 PM, Sandra Loosemore wrote:
2018-07-23 Jojo
Huibin Wang
Sandra Loosemore
Chung-Lin Tang
C-SKY port: Backend implementation
gcc/
* config/csky/*: New.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86448
--- Comment #2 from kelvin at gcc dot gnu.org ---
Using the GCC8 branch, svn version id 262483 (the same version tested by
Michael), I'm getting the following results:
-mcpu=power8-mcpu=power9
28.57
This PR shows a pathological case in which we try SLP vectorisation on
dead code. We record that 0 bits of the result are enough to satisfy
all users (which is true), and that led to precision being 0 in:
static unsigned int
vect_element_precision (unsigned int precision)
{
precision = 1 <<
On Mon, Jul 23, 2018 at 10:26:35PM -0600, Sandra Loosemore wrote:
> diff --git a/libgcc/config.host b/libgcc/config.host
> index 18cabaf..b2ee0c9 100644
> --- a/libgcc/config.host
> +++ b/libgcc/config.host
> @@ -94,6 +94,9 @@ am33_2.0-*-linux*)
> arc*-*-*)
> cpu_type=arc
> ;;
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86618
--- Comment #4 from rsandifo at gcc dot gnu.org
---
Author: rsandifo
Date: Tue Jul 24 18:08:19 2018
New Revision: 262951
URL: https://gcc.gnu.org/viewcvs?rev=262951=gcc=rev
Log:
Avoid _VINFO_MASKS for bb vectorisation (PR 86618)
r262589
r262589 introduced another instance of the bug fixed in r258131.
Tested on aarch64-linux-gnu and applied as obvious.
Richard
2018-07-24 Richard Sandiford
gcc/
PR tree-optimization/86618
* tree-vect-stmts.c (vectorizable_call): Don't take the address
of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86654
--- Comment #11 from Richard Biener ---
OK, so patch at least regresses
FAIL: g++.dg/debug/dwarf2/lambda1.C -std=gnu++11 scan-assembler-times
DW_TAG_variable[^.]*.ascii "this.0" 2
FAIL: g++.dg/debug/dwarf2/lambda1.C -std=gnu++14
On Mon, Jul 9, 2018 at 6:40 PM Richard Earnshaw
wrote:
>
>
> This patch defines a new intrinsic function
> __builtin_speculation_safe_value. A generic default implementation is
> defined which will attempt to use the backend pattern
> "speculation_safe_barrier". If this pattern is not defined,
This patch allows combine to combine two insns into two. This helps
in many cases, by reducing instruction path length, and also allowing
further combinations to happen. PR85160 is a typical example of code
that it can improve.
This patch does not allow such combinations if either of the
On Tue, Jul 24, 2018 at 4:41 PM Jakub Jelinek wrote:
>
> On Tue, Jul 24, 2018 at 04:33:30PM +0200, Richard Biener wrote:
> > DW_OP_GNU_variable_value you mean. That's true. But I was talking about
>
> Sure.
>
> > omitting DW_AT_upper_bound which would correspond to int[] vs.
> > a empty
On Mon, 2018-07-23 at 20:56 -0600, Martin Sebor wrote:
> On 07/23/2018 07:20 PM, David Malcolm wrote:
> > On Mon, 2018-07-23 at 17:49 -0600, Martin Sebor wrote:
> > > (David, I'm hoping your your help here. Please see the end.)
> > >
> > > While looking into a recent -Warray-bounds instance in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85476
chefmax at gcc dot gnu.org changed:
What|Removed |Added
CC||m.ostapenko at samsung dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86656
Bug 86656 depends on bug 80798, which changed state.
Bug 80798 Summary: Dynamic stack buffer (alloca) overflow in ObjC compiler.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80798
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80798
chefmax at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85610
Segher Boessenkool changed:
What|Removed |Added
CC||segher at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85925
--- Comment #4 from Segher Boessenkool ---
Any progress with this PR?
Hi Richard,
Thanks for the review!
The 07/23/2018 18:46, Richard Biener wrote:
> On July 23, 2018 7:01:23 PM GMT+02:00, Tamar Christina
> wrote:
> >Hi All,
> >
> >This allows copy_blkmode_to_reg to perform larger copies when it is
> >safe to do so by calculating
> >the bitsize per iteration
On July 24, 2018 5:50:33 PM GMT+02:00, Ramana Radhakrishnan
wrote:
>On Thu, Jul 19, 2018 at 10:11 AM, Richard Biener
>wrote:
>>
>> Status
>> ==
>>
>> The GCC 8 branch is frozen for preparation of the GCC 8.2 release.
>> All changes to the branch now require release manager approval.
>>
>>
On July 24, 2018 5:50:33 PM GMT+02:00, Ramana Radhakrishnan
wrote:
>On Thu, Jul 19, 2018 at 10:11 AM, Richard Biener
>wrote:
>>
>> Status
>> ==
>>
>> The GCC 8 branch is frozen for preparation of the GCC 8.2 release.
>> All changes to the branch now require release manager approval.
>>
>>
On 07/23/2018 02:14 PM, Sam Tebbs wrote:
On 07/23/2018 12:38 PM, Renlin Li wrote:
+(define_insn "*aarch64_bfxil"
+ [(set (match_operand:GPI 0 "register_operand" "=r,r")
+ (ior:GPI (and:GPI (match_operand:GPI 1 "register_operand" "r,0")
+ (match_operand:GPI 3
2018-07-24 17:41 GMT+02:00 Janne Blomqvist :
> Optimization bugs that pop up at different optimization levels are hard
> enough for users to figure out
Right, and they're impossible to detect if there is no way to disable
the optimization, which is what this PR is about.
> without the frontend
On 07/24/2018 01:59 AM, Bernd Edlinger wrote:
Hi!
This patch makes strlen range computations more conservative.
Firstly if there is a visible type cast from type A to B before passing
then value to strlen, don't expect the type layout of B to restrict the
possible return value range of strlen.
1 - 100 of 291 matches
Mail list logo
