Hi Paul,
That is very well done. Thanks for picking it up and running with it.
OK on both the fix and the dumping of the gsymbols.
Committed, thanks.
You might consider back porting both this patch and my fix for the
original bug to 9-branch.
Both patches apply cleanly together on gcc-9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91296
Bug ID: 91296
Summary: ICE when passing complex number %re/%im as a procedure
argument with -Waliasing.
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
On (07/30/19 14:12), Sergey Senozhatsky wrote:
> On (07/29/19 09:42), Jonathan Wakely wrote:
> > Please don't cross-post to te gcc@ and gcc-bugs@ lists, that's never
> > appropriate.
>
> So is top-posing ;)
D'oh... s/posing/posting/
Will keep in mind next time that gcc team prefers bugzilla.
On (07/29/19 09:42), Jonathan Wakely wrote:
> Please don't cross-post to te gcc@ and gcc-bugs@ lists, that's never
> appropriate.
So is top-posing ;)
> The gcc@ list is not for reporting bugs, and the
> gcc-bugs@ list is for automated emails sent from our Bugzilla
> database, also not for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91201
--- Comment #6 from Joel Yliluoma ---
Maybe a horizontal checksum is a bit obscure term. A 8-bit checksum is what is
being accomplished, nonetheless. Yes, there are simpler ways to do it…
But I tried a number of different approaches in order to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91295
Bug ID: 91295
Summary: [gdb] program crashed with segementation fault when
set breakpoint at address
Product: gcc
Version: 8.3.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91287
--- Comment #1 from Xiong Hu XS Luo ---
Martin's commit 4ee64e30659a9125a47eeea882d8044e690ce334 will cause ICE.
It's a REGRESSION not related to this current issue.
~/local/gcc_t/bin/gfortran -O3 -mcpu=power9 hellofortran.f90 -mveclibabi=mass
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90538
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91294
Martin Sebor changed:
What|Removed |Added
Keywords||wrong-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91294
Bug ID: 91294
Summary: [10 Regression] wrong strlen result of a conditional
with an offset
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91293
Bug ID: 91293
Summary: Wrong code with -O3
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91292
Bug ID: 91292
Summary: Mangler incorrectly handles negative numbers in
expressions
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Severity: normal
Attached patch allows only SUBREGs as output operands to movstrict
expander and further allows only register operand outputs in various
corresponding splitters. This enforces the restriction, as documented
for STRICT_LOW_PART RTX:
This expression code is used in only one context: as the
Ping.
Steve Ellcey
sell...@marvell.com
On Mon, 2019-07-22 at 11:25 -0700, Steve Ellcey wrote:
> On Fri, 2019-07-19 at 19:24 +0100, Richard Sandiford wrote:
> >
> > You can probably also remove:
> >
> > tree new_type = build_distinct_type_copy (TREE_TYPE (node-
> > >decl));
> > ...
On 12/07/2019 12:38 pm, Kwok Cheung Yeung wrote:
This patch fixes a similar situation that occurs with the use_device
clause, where the lowering would result in a null dereference if applied
to a non-present optional argument. This patch builds a conditional
check that skips the dereference if
On 12/07/2019 12:41 pm, Jakub Jelinek wrote:
+/* Return true if DECL is a Fortran optional argument. */
+
+bool
+omp_is_optional_argument (tree decl)
+{
+ /* A passed-by-reference Fortran optional argument is similar to
+ a normal argument, but since it can be null the type is a
+
On Wed, 24 Jul 2019 09:31:11 -0600
Jeff Law wrote:
> On 7/23/19 7:22 AM, Jozef Lawrynowicz wrote:
> >
> > gcc/ChangeLog:
> >
> > 2019-07-23 Jozef Lawrynowicz
> >
> > * config/msp430/msp430.h (DRIVER_SELF_SPECS): Define and emit errors
> > when -m{code,data}-region are used without
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91283
--- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #1 from Jakub Jelinek ---
> Created attachment 46635
> --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46635=edit
> gcc10-pr91283.patch
>
> Untested fix.
FWIW, I've
-linux-gnu
Between 20190728 (r273850) and 20190729 (r273879), gcc.dg/20020312-2.c started
to FAIL:
+FAIL: gcc.dg/20020312-2.c (internal compiler error)
+FAIL: gcc.dg/20020312-2.c (test for excess errors)
+UNRESOLVED: gcc.dg/20020312-2.c compilation failed to produce executable
I'm seeing it on 32
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91201
--- Comment #5 from Marc Glisse ---
It looks like a convoluted way to write:
unsigned char sum()
{
unsigned char res=0;
unsigned char*p=(unsigned char*)bytes;
for(int n=0;n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70320
--- Comment #1 from jozefl at gcc dot gnu.org ---
Author: jozefl
Date: Mon Jul 29 19:21:18 2019
New Revision: 273883
URL: https://gcc.gnu.org/viewcvs?rev=273883=gcc=rev
Log:
Allow both upper and lower case 'r' in register names
2019-07-29
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91242
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Hi!
On Mon, Jul 29, 2019 at 07:37:53PM +0200, Martin Jambor wrote:
> as you might know, Tejas is our Google Summer of Code student working on
> adding built-in functions for some new math functions added in ISO/IEC
> TS 18661.
>
> His next step is to expand "functions rounding result to narrower
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89330
Andreas Schwab changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
Hello Feng,
first, sorry for the terrible delay in reviewing, but here is one now :)
Generally I do like the idea of the transformation, and the basic building
blocks seem to be sound. But I dislike it being a separate pass, so
please integrate the code you have written into the existing loop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90813
--- Comment #33 from Thomas Koenig ---
Author: tkoenig
Date: Mon Jul 29 17:45:24 2019
New Revision: 273880
URL: https://gcc.gnu.org/viewcvs?rev=273880=gcc=rev
Log:
2019-07-29 Thomas Koenig
PR fortran/90813
*
Hi Segher,
as you might know, Tejas is our Google Summer of Code student working on
adding built-in functions for some new math functions added in ISO/IEC
TS 18661.
His next step is to expand "functions rounding result to narrower type"
(so fadd, fsub and possibly fmul and fdiv described in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91258
--- Comment #7 from Martin Sebor ---
We need to put a breakpoint in the block below in
strlen_check_and_optimize_stmt and print the lhs node and its type (p
debug_tree (lhs)) to explain how is_char_store is set to true for the
unexpected
Please send patch series as patch series. It is almost impossible to
keep track of a patch series as unrelated emails, even worse than the
other way around.
Please keep subjects to about 50 chars max., distinguishable in the
first 30 or so chars, so that patches can actually be found in mail
Hi,
On Sat, Jul 27 2019, Tejas Joshi wrote:
> Hello.
>
>>> You'll need something different from CASE_MATHFN - these are a different
>>> kind of functions that need handling in a different way, because they are
>>> parametrized over certain *pairs* of types, rather than over a single
>>> type.
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91290
Bug ID: 91290
Summary: pragma maybe-uninitialized does not propagate to
lambda
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Currently the Arm backend selects the alternative sched pressure algorithm.
The issue is that this doesn't take register pressure into account, and so
it causes significant additional spilling on Arm where there are only 14
allocatable registers. SPEC2006 shows significant codesize reduction
with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91289
Bug ID: 91289
Summary: powerpc-eabi: Usage of -fstack-limit-symbol leads to
internal compiler error during RTL pass
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Hi Joseph,
can you please have look at this patch from Tejas, whether it is perhaps
ready to be committed to trunk or what things still need to be
addressed?
Thanks a lot,
Martin
On Fri, Jun 28 2019, Tejas Joshi wrote:
> Hi.
> This patch includes implementation of new function roundeven
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91190
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
On Wed, Jul 24, 2019 at 12:07:36PM -0600, Martin Sebor wrote:
> > > There are a number of existing instances of setting TREE_NO_WARNING
> > > to suppress -Wuninitialized, and some are the cause of known problems.
> > > Bugs 51545, 58950, 74762, 74765 or 89697 are examples. They all boil
> > >
On Tue, Jul 23, 2019 at 04:26:24AM +, JiangNing OS wrote:
> --- a/gcc/ChangeLog
> +++ b/gcc/ChangeLog
> @@ -1,3 +1,9 @@
> +2019-07-22 Jiangning Liu
> +
> + PR middle-end/91195
> + * tree-ssa-phiopt.c (cond_store_replacement): Work around
> + -Wmaybe-uninitialized warning.
> +
>
Hi all,
The builtins from use fairly general expander names such as
"crc", "mcr" etc.
These run the risk of being reserved by the midend in the future.
Let's namespace them to arm_* as is convention.
Bootstrapped and tested on arm-none-linux-gnueabihf.
Committing to trunk.
Thanks,
Kyrill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91157
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
On Sunday, 28 July 2019 16:16:21 PDT Kevin Weidemann wrote:
> Hello everyone,
>
> I have recently randomly discovered the fact, that building with
> `-march=ivybridge` does not necessarily produce the same output as
> `-march=native` on an Intel Core i7 3770K (Ivy Bridge).
>
> In particular,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91192
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91227
--- Comment #15 from Martin Sebor ---
I agree that comparison of the intptr_t values would be preferable over
extending the pointer inequality semantics. It's the intended mechanism for
this sort query. It makes code that relies on the
在 2019/7/29 22:43, JonY 写道:
>
> Any updates?
>
No. I am still under the impression that using thread handles as
`std::thread::id`s:
0) complexifies comparison of thread IDs without obvious benefits, and
1) does not work reliably because handles can be duplicated, and
2) makes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91285
--- Comment #2 from Konrad Schwarz ---
Thank you for your suggestion -- it does indeed work.
However, this is a workaround for this specific problem --
other pragmas cannot be handled in this way --
consider # pragma GCC optimize ... or #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91192
Jakub Jelinek changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91259
--- Comment #7 from Casey Carter ---
Thanks, Jonathan. I can confirm that grepping for "\b(concept|requires)\b"
finds a great many uses in comments, but only the one concept definition and
one requires-clause in .
On 7/3/19 12:55 PM, Liu Hao wrote:
> 在 2019/7/2 下午8:27, Jonathan Wakely 写道:
>>
>> What do you mean by "unclosed thread"? If I read it correctly, the MSDN
>> page
>> refers to closing a handle (which makes sense), not closing a thread.
>>
>
> Yes, it meant a thread which has terminated but not
The following patch addresses appearant quadraticness in PTAs
SCC merging algorithm which does (simplified)
for (node N in SCC)
bitmap_ior_into (pred(leader), pred(N));
with the linked list implementation this leads to increasingly large
amount of walking for pred(leader).
The patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91285
--- Comment #1 from Andrew Pinski ---
Isn't it better to do:
# defineENCLOSING_OBJECT(TYPE, MEMBER, OBJECT)\
((void)sizeof (&((TYPE *) 0)->MEMBER - OBJECT),\
(TYPE *) ((char *) OBJECT - offsetof (TYPE, MEMBER)))
On Mon, Jul 29, 2019 at 12:37 PM Martin Liška wrote:
>
> On 7/29/19 11:59 AM, Richard Biener wrote:
> > On Sun, Jul 28, 2019 at 4:57 PM Martin Liška wrote:
> >>
> >> Hi.
> >>
> >> And there's one more patch that deals with delete operator
> >> which has a second argument (size). That definition
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51333
--- Comment #9 from Jonathan Wakely ---
Fixed on trunk so far.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51333
--- Comment #8 from Jonathan Wakely ---
Author: redi
Date: Mon Jul 29 14:27:19 2019
New Revision: 273878
URL: https://gcc.gnu.org/viewcvs?rev=273878=gcc=rev
Log:
PR libstdc++/51333 Define recursive_init_error constructor non-inline
The
The recursive_init_error class is defined in a header, with an inline
constructor, but the definition of the vtable and destructor are not
exported from the shared library. With -fkeep-inline-functions the
constructor gets emitted in user code, and requires the (non-exported)
vtable. This fails
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91257
--- Comment #5 from Richard Biener ---
Author: rguenth
Date: Mon Jul 29 14:19:07 2019
New Revision: 273877
URL: https://gcc.gnu.org/viewcvs?rev=273877=gcc=rev
Log:
2019-07-29 Richard Biener
PR tree-optimization/91257
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91259
David Stone changed:
What|Removed |Added
CC||david at doublewise dot net
--- Comment
On Mon, Jul 29, 2019 at 3:06 PM Richard Sandiford
wrote:
>
> Richard Sandiford writes:
> > Richard Biener writes:
> >> On Mon, Jul 29, 2019 at 11:11 AM Richard Sandiford
> >> wrote:
> >>>
> >>> inchash::hash::add_wide_int operated directly on the raw encoding
> >>> of the wide_int, including
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91150
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
Hi Martin.
In SVN r273662 you changed a comment in avr.c from __gnu_lto_v1 to
__gnu_lto_slim without changing the relevant code:
/* __gnu_lto_slim is just a marker for the linker injected by toplev.c.
There is no need to trigger __do_clear_bss code for them. */
if (!STR_PREFIX_P
Hi.
The patch is about proper error message for situations where
user give a wrong argument to -flto option.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be installed?
Thanks,
Martin
gcc/ChangeLog:
2019-07-29 Martin Liska
* opts.c
Hi.
I'm sending v2 of the patch that can newly auto-detect make
jobserver and use it.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be installed?
Thanks,
Martin
>From df747a46241dcdb8ad055071f9e0605c9f469268 Mon Sep 17 00:00:00 2001
From: Martin Liska
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91256
--- Comment #2 from Danack at basereality dot com ---
Apparently this might be fixable by calling:
omp_pause_resource_all(omp_pause_hard);
However, that function is only defined in OpenMP version 5, which isn't
available in the versions of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91288
--- Comment #2 from Martin Liška ---
Created attachment 46637
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46637=edit
2.ii
Richard Sandiford writes:
> Richard Biener writes:
>> On Mon, Jul 29, 2019 at 11:11 AM Richard Sandiford
>> wrote:
>>>
>>> inchash::hash::add_wide_int operated directly on the raw encoding
>>> of the wide_int, including any redundant upper bits. The problem
>>> with that is that the upper bits
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91288
--- Comment #1 from Martin Liška ---
Created attachment 46636
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46636=edit
1.ii
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91288
Bug ID: 91288
Summary: [8/9/10 Regression] ICE in add_symbol_to_partition_1,
at lto/lto-partition.c:153 since r249224
Product: gcc
Version: 10.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91287
Bill Schmidt changed:
What|Removed |Added
Keywords||lto, wrong-code
Target|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91287
Bug ID: 91287
Summary: LTO disables linking with scalar MASS library (Fortran
only)
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91282
Tamar Christina changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |tnfchris at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91284
Richard Earnshaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91286
Bug ID: 91286
Summary: invalid use of incomplete type depends on
--enable-checking=release
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
The following patch addresses a known issue with managing availability
in RPO VN - this is just the first time a testcase actually shows
measurable cycles here. It's hammering libc malloc/free for
allocating one-element vectors. So the following finally goes the
way the comment suggests and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51333
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |ASSIGNED
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91285
Bug ID: 91285
Summary: _Pragma does not work in a useful fashion
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91280
--- Comment #2 from Martin Liška ---
(In reply to Richard Biener from comment #1)
> Hmm, this has earlier errors:
>
> t.ii:123:20: error: invalid use of incomplete type ‘class
> TensorMap, 0>’
> 123 | static const int NumInputDims = H
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91280
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |8.4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91201
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91283
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91273
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |7.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91267
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91257
--- Comment #4 from Richard Biener ---
Author: rguenth
Date: Mon Jul 29 11:38:46 2019
New Revision: 273876
URL: https://gcc.gnu.org/viewcvs?rev=273876=gcc=rev
Log:
2019-07-29 Richard Biener
PR tree-optimization/91257
*
The following significantly brings down compile-time spent in VRP
for the testcase.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
2019-07-29 Richard Biener
PR tree-optimization/91257
* tree-vrp.c (operand_less_p): Avoid dispatching to fold
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91257
Richard Biener changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91273
--- Comment #7 from Jan Hubicka ---
aha, relies on indentation of common in 2.F. i will check what goes wrong.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91273
--- Comment #6 from Martin Liška ---
(In reply to Jan Hubicka from comment #3)
> Still works for me
> hubicka@lomikamen-jh:~$ /aux/hubicka/trunk-install/bin/g++ 1.ii 2.F -O2 -flto
> /usr/local/bin/ld: /tmp/ccpfzvWm.ltrans0.ltrans.o: in function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91273
--- Comment #5 from Martin Liška ---
Created attachment 46634
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46634=edit
2.F
Richard Biener writes:
> On Mon, Jul 29, 2019 at 11:11 AM Richard Sandiford
> wrote:
>>
>> inchash::hash::add_wide_int operated directly on the raw encoding
>> of the wide_int, including any redundant upper bits. The problem
>> with that is that the upper bits are only defined for some wide-int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91273
--- Comment #4 from Martin Liška ---
Created attachment 46633
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46633=edit
1.ii
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91273
--- Comment #3 from Jan Hubicka ---
Still works for me
hubicka@lomikamen-jh:~$ /aux/hubicka/trunk-install/bin/g++ 1.ii 2.F -O2 -flto
/usr/local/bin/ld: /tmp/ccpfzvWm.ltrans0.ltrans.o: in function `main':
:(.text.startup+0x5): undefined reference
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91273
--- Comment #2 from Martin Liška ---
(In reply to Jan Hubicka from comment #1)
> This seems to work for me with current trunk
No, it's broken also on current trunk.
>
> hubicka@lomikamen-jh:/aux/hubicka/trunk4/build2/gcc$ cat ~/1.ii
> extern
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91265
Martin Liška changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91265
--- Comment #4 from Martin Liška ---
Fixed with r273875:
2019-07-29 Martin Liska
* tree-ssa-dce.c (eliminate_unnecessary_stmts): Do not
remove LHS of operator new call. It's handled latter.
On 7/29/19 11:59 AM, Richard Biener wrote:
> On Sun, Jul 28, 2019 at 4:57 PM Martin Liška wrote:
>>
>> Hi.
>>
>> And there's one more patch that deals with delete operator
>> which has a second argument (size). That definition GIMPLE
>> statement of the size must be also properly marked.
>>
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91284
Bug ID: 91284
Summary: Gcc for aarch64 binaries
Product: gcc
Version: 8.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Hello,
I missed your email initially, so sorry for late reaction.
> > +/* REF1 and REF2 are ARRAY_REFs which either start at the same address or
> > + are completely disjoint.
>
> So the ARRAY_REF array bases are at the same address, not the ARRAY_REF
> itself?
Yes, updated the comment.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91273
--- Comment #1 from Jan Hubicka ---
This seems to work for me with current trunk
hubicka@lomikamen-jh:/aux/hubicka/trunk4/build2/gcc$ cat ~/1.ii
extern "C" {
struct {
} ltregul_;
}
hubicka@lomikamen-jh:/aux/hubicka/trunk4/build2/gcc$ cat ~/2.F
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91267
--- Comment #11 from Richard Biener ---
Author: rguenth
Date: Mon Jul 29 10:10:15 2019
New Revision: 273874
URL: https://gcc.gnu.org/viewcvs?rev=273874=gcc=rev
Log:
2019-07-29 Richard Biener
PR tree-optimization/91267
*
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2019-07-29 Richard Biener
PR tree-optimization/91267
* vr-values.c (vr_values::update_value_range): Add early return
for effectively VARYING lattice entry.
* gcc.dg/torture/pr91267.c:
On Mon, Jul 29, 2019 at 11:11 AM Richard Sandiford
wrote:
>
> inchash::hash::add_wide_int operated directly on the raw encoding
> of the wide_int, including any redundant upper bits. The problem
> with that is that the upper bits are only defined for some wide-int
> storage types (including
On Sun, Jul 28, 2019 at 4:57 PM Martin Liška wrote:
>
> Hi.
>
> And there's one more patch that deals with delete operator
> which has a second argument (size). That definition GIMPLE
> statement of the size must be also properly marked.
>
> Patch can bootstrap on x86_64-linux-gnu and survives
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91259
--- Comment #5 from Jonathan Wakely ---
(In reply to David Stone from comment #0)
> libstdc++ contains many expressions that are not parenthesized
Many?
> that do not meet these requirements (this was not true of the Concepts TS,
> but as
1 - 100 of 126 matches
Mail list logo
