[Bug tree-optimization/86724] Compilation error with new isl 0.20 (missing includes)

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86724

--- Comment #3 from Richard Biener  ---
Author: rguenth
Date: Wed Aug  1 07:21:08 2018
New Revision: 263193

URL: https://gcc.gnu.org/viewcvs?rev=263193&root=gcc&view=rev
Log:
2018-08-01  Richard Biener  

PR bootstrap/86724
* graphite.h: Include isl/id.h and isl/space.h to allow build
with ISL 0.20.

Modified:
trunk/gcc/ChangeLog
trunk/gcc/graphite.h

[Bug debug/86687] Wrong debug information for string types passed as parameters

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86687

Richard Biener  changed:

   What|Removed |Added

  Known to work||9.0

--- Comment #11 from Richard Biener  ---
Fixed on trunk sofar.

[Bug target/86752] [9 Regression] FAIL: gcc.target/i386/avx2-cvt-2.c

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86752

Richard Biener  changed:

   What|Removed |Added

   Target Milestone|--- |9.0
Summary|FAIL:   |[9 Regression] FAIL:
   |gcc.target/i386/avx2-cvt-2. |gcc.target/i386/avx2-cvt-2.
   |c   |c

[Bug target/86753] [9 Regression] gcc.target/aarch64/sve/vcond_[45].c fail after recent combine patch

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86753

Richard Biener  changed:

   What|Removed |Added

Version|unknown |9.0
   Target Milestone|--- |9.0
Summary|gcc.target/aarch64/sve/vcon |[9 Regression]
   |d_[45].c fail after recent  |gcc.target/aarch64/sve/vcon
   |combine patch   |d_[45].c fail after recent
   ||combine patch

[Bug target/86763] [8/9 Regression] Wrong code comparing member of copy of a 237 byte object with nontrivial default constructor on x86-64 arch

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86763

Richard Biener  changed:

   What|Removed |Added

   Keywords||wrong-code
 Target|x86_64- |x86_64-*-*
   Priority|P3  |P2
 CC||uros at gcc dot gnu.org
   Target Milestone|--- |8.3

--- Comment #3 from Richard Biener  ---
RTL expansion shows different alignment of some stack vars, -O1
-fstrict-aliasing is also broken.  Assembler difference -O1 vs. -O2 is

 main:
@@ -45,24 +48,24 @@
subq$488, %rsp
.cfi_def_cfa_offset 496
call_Z8init_msgv
-   movq%rax, (%rsp)
-   movq%rdx, 8(%rsp)
-   leaq240(%rsp), %rdi
-   movq%rsp, %rsi
+   movq%rsp, %rdi
movl$29, %ecx
+   leaq240(%rsp), %rsi
+   movq%rax, 240(%rsp)
+   cmpq$1001, 8(%rsp)
+   movq%rdx, 248(%rsp)
rep movsq
movl(%rsi), %eax
movl%eax, (%rdi)
movzbl  4(%rsi), %eax
movb%al, 4(%rdi)
-   cmpq$1001, 248(%rsp)
-   jne .L7
-   movl$0, %eax
+   jne .L8
+   xorl%eax, %eax
addq$488, %rsp
.cfi_remember_state
.cfi_def_cfa_offset 8
ret
-.L7:
+.L8:
.cfi_restore_state


see how the compare is moved very far away from the branch possibly across
flag clobbering insns (rep movsq?).  Target sounds good.

[Bug libstdc++/86751] [6/7/8 Regression] Ambiguous operator= overload for std::pair

[m.cencora at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86751

--- Comment #4 from m.cencora at gmail dot com ---
That was fast, thanks a lot!
Confirming with compiler explorer - this is fixed on trunk.

[Bug target/86770] New: UNRESOLVED: 30_threads/call_once/call_once1.cc compilation failed to produce executable

[belyshev at depni dot sinp.msu.ru]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86770

Bug ID: 86770
   Summary: UNRESOLVED: 30_threads/call_once/call_once1.cc
compilation failed to produce executable
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Keywords: link-failure
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: belyshev at depni dot sinp.msu.ru
  Target Milestone: ---
Target: riscv64-unknown-linux-gnu

Everything under 30_threads/ fail to link on riscv with -Wl,--gc-sections. 
Short testcase:

$ cat > bug.cc <

[Bug libstdc++/86751] [6/7/8 Regression] Ambiguous operator= overload for std::pair

[m.cencora at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86751

--- Comment #5 from m.cencora at gmail dot com ---
That was fast, thanks a lot!
Confirmed with compiler explorer - this is fixed on trunk.

[Bug target/86763] [8/9 Regression] Wrong code comparing member of copy of a 237 byte object with nontrivial default constructor on x86-64 arch

[ubizjak at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86763

--- Comment #4 from Uroš Bizjak  ---
(In reply to Richard Biener from comment #3)
> see how the compare is moved very far away from the branch possibly across
> flag clobbering insns (rep movsq?).  Target sounds good.

No, rep movsq doesn't clobber flags [1].

[1] http://www.felixcloutier.com/x86/MOVS:MOVSB:MOVSW:MOVSD:MOVSQ.html

[Bug testsuite/86766] new test case c-c++-common/spec-barrier-1.c introduced in r263168 fails

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86766

--- Comment #1 from Richard Biener  ---
I think the failure was desired so you fixup your target

[Bug c++/86767] [6/7/8/9 Regression] continue statements in constexpr functions causes unbounded looping

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86767

Richard Biener  changed:

   What|Removed |Added

   Priority|P3  |P2
  Known to work||6.2.0
   Target Milestone|--- |6.5
Summary|continue statements in  |[6/7/8/9 Regression]
   |constexpr functions causes  |continue statements in
   |unbounded looping   |constexpr functions causes
   ||unbounded looping
  Known to fail||6.3.0, 7.1.0, 8.1.0, 9.0

--- Comment #1 from Richard Biener  ---
Regressed on the GCC 6 branch - GCC 6.2 works for me.  Some GCCs chose to
not hang but diagnose it like

t.C: In function ‘void test()’:
t.C:17:33:   in constexpr expansion of ‘sampleFn()’
t.C:8:9: error: constexpr loop iteration count exceeds limit of 262144 (use
-fconstexpr-loop-limit= to increase the limit)
 for (int j = 0; j < 10; ++j ) {}
 ^~~

[Bug c/86768] gcc wrongly decides that variable is <=1 after "while (x>1 && blah)" construct.

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86768

Richard Biener  changed:

   What|Removed |Added

 Status|RESOLVED|NEW
   Last reconfirmed||2018-08-01
 CC||rguenth at gcc dot gnu.org
 Resolution|INVALID |---
 Ever confirmed|0   |1

--- Comment #2 from Richard Biener  ---
Well, it is unfortunate that VRP performs threading to isolate a never executed
case.  That's similar to array-bound warnings emitted by VRP2 which we
disabled because of unrolling exposing them.

Yes, theoretically you didn't constrain inputs locally but you may very
well have in all callers.  GCC isn't supposed to warn here.

Better move those warnings earlier like we ended up doing for -Warray-bounds.

They are currently emitted by RTL expansion, correct?

[Bug tree-optimization/86724] Compilation error with new isl 0.20 (missing includes)

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86724

--- Comment #4 from Richard Biener  ---
Author: rguenth
Date: Wed Aug  1 08:06:20 2018
New Revision: 263194

URL: https://gcc.gnu.org/viewcvs?rev=263194&root=gcc&view=rev
Log:
2018-08-01  Richard Biener  

PR bootstrap/86724
* graphite.h: Include isl/id.h and isl/space.h to allow build
with ISL 0.20.

Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/graphite.h

[Bug tree-optimization/86724] Compilation error with new isl 0.20 (missing includes)

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86724

--- Comment #5 from Richard Biener  ---
Author: rguenth
Date: Wed Aug  1 08:07:16 2018
New Revision: 263195

URL: https://gcc.gnu.org/viewcvs?rev=263195&root=gcc&view=rev
Log:
2018-08-01  Richard Biener  

PR bootstrap/86724
* graphite.h: Include isl/id.h and isl/space.h to allow build
with ISL 0.20.

Modified:
branches/gcc-7-branch/gcc/ChangeLog
branches/gcc-7-branch/gcc/graphite.h

[Bug tree-optimization/86724] Compilation error with new isl 0.20 (missing includes)

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86724

Richard Biener  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Known to work||7.3.1, 8.2.1, 9.0
 Resolution|--- |FIXED
  Known to fail||6.4.0, 7.3.0, 8.2.0

--- Comment #6 from Richard Biener  ---
Fixed for GCC 7.4+.

[Bug middle-end/86771] New: gfortran.dg/actual_array_constructor_1.f90 fails on arm after combine 2 insns to 2 insns patch

[clyon at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86771

Bug ID: 86771
   Summary: gfortran.dg/actual_array_constructor_1.f90 fails on
arm after combine 2 insns to 2 insns patch
   Product: gcc
   Version: 6.4.1
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: middle-end
  Assignee: unassigned at gcc dot gnu.org
  Reporter: clyon at gcc dot gnu.org
  Target Milestone: ---

Hi,

After r263067 (combine: Allow combining two insns to two insns),
I have noticed that
FAIL: gfortran.dg/actual_array_constructor_1.f90   -O1  execution test
on arm-none-linux-gnueabi --with-cpu cortex-a9
on arm-none-linux-gnueabihf --with-cpu cortex-a9 --with-fpu neon-fp16

no such regression on:
arm-none-linux-gnueabihf --with-cpu cortex-a15 --with-fpu neon-vfpv4
arm-none-linux-gnueabihf --with-cpu cortex-a57 --with-fpu crypto-neon-fp-armv8

[Bug rtl-optimization/86763] [8/9 Regression] Wrong code comparing member of copy of a 237 byte object with nontrivial default constructor on x86-64 arch

[ubizjak at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86763

Uroš Bizjak  changed:

   What|Removed |Added

 CC|uros at gcc dot gnu.org|ubizjak at gmail dot com
  Component|target  |rtl-optimization

--- Comment #5 from Uroš Bizjak  ---
(In reply to Richard Biener from comment #3)
> see how the compare is moved very far away from the branch possibly across
> flag clobbering insns (rep movsq?).  Target sounds good.

Scheduler (sched2) pass is moving the compare:

(insn 21 17 22 2 (set (reg:CCZ 17 flags)
(compare:CCZ (mem/c:DI (plus:DI (reg/f:DI 7 sp)
(const_int 8 [0x8])) [1 MEM[(struct Msg &)&t].id+0 S8 A64])
(const_int 1001 [0x3e9]))) "t4.cpp":32 12 {*cmpdi_1}
 (nil))

in front of rep movsd:

(insn 11 10 12 2 (parallel [
(set (reg:DI 2 cx [92])
(const_int 0 [0]))
(set (reg/f:DI 5 di [90])
(plus:DI (ashift:DI (reg:DI 2 cx [92])
(const_int 3 [0x3]))
(reg/f:DI 5 di [90])))
(set (reg/f:DI 4 si [91])
(plus:DI (ashift:DI (reg:DI 2 cx [92])
(const_int 3 [0x3]))
(reg/f:DI 4 si [91])))
(set (mem/c:BLK (reg/f:DI 5 di [90]) [7 MEM[(struct T *)&t]+0 S232
A128])
(mem/c:BLK (reg/f:DI 4 si [91]) [7 MEM[(struct T *)&D.2891]+0
S232 A128]))
(use (reg:DI 2 cx [92]))
]) "t4.cpp":31 993 {*rep_movdi_rex64}
 (expr_list:REG_UNUSED (reg:DI 2 cx [92])
(nil)))

Scheduler doesn't notice that rep movsd target overlaps compare operand.

Looks like rtl-optimization (scheduler) to me.

[Bug target/82005] Early lto debug not implemented on Darwin

[iains at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82005

--- Comment #48 from Iain Sandoe  ---
the relocations look reasonable and dwarfdump of the individual objects
(.debug.temp.o and the .ltrans0.ltans.o) also.

So, it looks like dsymutil isn't somehow consuming this so some debugging is
needed there.

I guess if this can be fixed in upstream dsymutil, it will eventually get to
Xcode - and in the meantime maybe we can have a config test for debug support
and disable in darwin.c on that.

TODO: debug dsymutil handling of this.

[Bug c++/86769] g++ destroys condition variable in for statement too early

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86769

Jonathan Wakely  changed:

   What|Removed |Added

   Keywords||wrong-code
 Status|UNCONFIRMED |NEW
   Last reconfirmed||2018-08-01
 Ever confirmed|0   |1

[Bug target/82005] Early lto debug not implemented on Darwin

[rguenther at suse dot de]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82005

--- Comment #49 from rguenther at suse dot de  ---
On Wed, 1 Aug 2018, iains at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82005
> 
> --- Comment #48 from Iain Sandoe  ---
> the relocations look reasonable and dwarfdump of the individual objects
> (.debug.temp.o and the .ltrans0.ltans.o) also.
> 
> So, it looks like dsymutil isn't somehow consuming this so some debugging is
> needed there.

But the interesting piece then is to somehow preserve the ltrans
objects since that is needed when the debug is not linked into
the executable?  Or is dsymutil extracting the debug from objects
and stores it somewhere more persistent?

> I guess if this can be fixed in upstream dsymutil, it will eventually get to
> Xcode - and in the meantime maybe we can have a config test for debug support
> and disable in darwin.c on that.
> 
> TODO: debug dsymutil handling of this.

[Bug c/85704] [8/9 Regression] cc1 run out of memory when it compile

[jakub at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85704

--- Comment #9 from Jakub Jelinek  ---
Author: jakub
Date: Wed Aug  1 09:10:31 2018
New Revision: 263198

URL: https://gcc.gnu.org/viewcvs?rev=263198&root=gcc&view=rev
Log:
PR c/85704
* c-typeck.c (init_field_decl_cmp): New function.
(output_pending_init_elements): Use it for field comparisons
instead of pure bit_position comparisons.

* gcc.c-torture/compile/pr85704.c: New test.

Added:
trunk/gcc/testsuite/gcc.c-torture/compile/pr85704.c
Modified:
trunk/gcc/c/ChangeLog
trunk/gcc/c/c-typeck.c
trunk/gcc/testsuite/ChangeLog

[Bug c++/86661] [9 Regression] g++ ICE:tree check: expected tree that contains ‘decl minimal’ structure, have ‘overload’ in note_name_declared_in_class, at cp/class.c:8288

[paolo.carlini at oracle dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86661

Paolo Carlini  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
   Last reconfirmed|2018-07-25 00:00:00 |2018-08-01
 CC|paolo.carlini at oracle dot com|
   Assignee|unassigned at gcc dot gnu.org  |paolo.carlini at oracle 
dot com
 Ever confirmed|0   |1

--- Comment #2 from Paolo Carlini  ---
Seems like we trivially want:

Index: class.c
===
--- class.c (revision 263197)
+++ class.c (working copy)
@@ -8285,7 +8285,7 @@ note_name_declared_in_class (tree name, tree decl)
 A name N used in a class S shall refer to the same declaration
 in its context and when re-evaluated in the completed scope of
 S.  */
-  if (permerror (DECL_SOURCE_LOCATION (decl),
+  if (permerror (location_of (decl),
 "declaration of %q#D changes meaning of %qD",
 decl, OVL_NAME (decl)))
inform (location_of ((tree) n->value),

[Bug target/82005] Early lto debug not implemented on Darwin

[iains at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82005

--- Comment #50 from Iain Sandoe  ---
(In reply to rguent...@suse.de from comment #49)
> On Wed, 1 Aug 2018, iains at gcc dot gnu.org wrote:
> 
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82005
> > 
> > --- Comment #48 from Iain Sandoe  ---
> > the relocations look reasonable and dwarfdump of the individual objects
> > (.debug.temp.o and the .ltrans0.ltans.o) also.
> > 
> > So, it looks like dsymutil isn't somehow consuming this so some debugging is
> > needed there.
> 
> But the interesting piece then is to somehow preserve the ltrans
> objects since that is needed when the debug is not linked into
> the executable?  Or is dsymutil extracting the debug from objects
> and stores it somewhere more persistent?

when an exe is linked, the static linker (ld64) does not include the debug data
in the exe.  However, it records (in the exe symbol table) the names of the
object files that it linked

dsymutil consumes the exe file table and the link line objects and links the
debug - producing a standard Darwin/OS X package structure containing the
linked debug. [by default name.dSYM] where "name" is the name of the exe.

So, yes that's moved it to a persistent place.

So 
case #1.
 - the link line objects are all temporaries (no save-temps).
 - in this case they must not be deleted until dsymutil has run, and AFAICS the
collect2 driver deals with that already.
 - my local patches remove the pre-link of the debug objects and emit those
onto the final link line (so it doesn't look any different from 'normal').  

case #2
 - with save temps, these objects need to be preserved
 - this isn't working with my current patch-set, it says [Leaving ... ] but the
ltrans0.ltran.o and the debug.temp.o files are removed unless I put -Wl,-debug
on the c/l.

.. also on the TODO to figure that out.

[Bug c/85704] [8/9 Regression] cc1 run out of memory when it compile

[jakub at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85704

--- Comment #10 from Jakub Jelinek  ---
Author: jakub
Date: Wed Aug  1 09:35:34 2018
New Revision: 263199

URL: https://gcc.gnu.org/viewcvs?rev=263199&root=gcc&view=rev
Log:
PR c/85704
* c-typeck.c (init_field_decl_cmp): New function.
(output_pending_init_elements): Use it for field comparisons
instead of pure bit_position comparisons.

* gcc.c-torture/compile/pr85704.c: New test.

Added:
branches/gcc-8-branch/gcc/testsuite/gcc.c-torture/compile/pr85704.c
Modified:
branches/gcc-8-branch/gcc/c/ChangeLog
branches/gcc-8-branch/gcc/c/c-typeck.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog

[Bug target/86772] New: [meta-bug] tracking port status for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772

Bug ID: 86772
   Summary: [meta-bug] tracking port status for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Keywords: meta-bug
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
  Target Milestone: ---

This is a meta bug to track the port status of all ports that have not yet been
updated to handle CVE-2017-5753 (Spectre variant 1).

If your port does (or might in the future) need to mitigate against unsafe
speculation, then you will need to define (at a minimum) a
"speculation_barrier" insn.

If your port does not (and never will in the future) need to mitigate against
unsafe speculation, you can simply add

#undef TARGET_HAVE_SPECULATION_SAFE_VALUE
#define TARGET_HAVE_SPECULATION_SAFE_VALUE speculation_safe_value_not_needed.

to your target defines.

[Bug target/86772] [meta-bug] tracking port status for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772

--- Comment #1 from Richard Earnshaw  ---
Original patch series and discussion can be found here: 

https://gcc.gnu.org/ml/gcc-patches/2018-07/msg01700.html

[Bug target/86774] New: Alpha port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86774

Bug ID: 86774
   Summary: Alpha port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: rth at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: alpha

The alpha port needs updating for this CVE.  See the linked meta-bug for
description of possible actions.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug c++/86773] New: GCC accepts junk before fold expressions

[mickey.veksler at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86773

Bug ID: 86773
   Summary: GCC accepts junk before fold expressions
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
  Assignee: unassigned at gcc dot gnu.org
  Reporter: mickey.veksler at gmail dot com
  Target Milestone: ---

template 
auto work(Param && ...param)
{
return ("hi" ... / param);
}

int main()
{
std::cout << work(1.0, 2.0, 5, 4.0) << "\n";
}


GCC simply ignores the "hi" junk before the fold expression, with no
diagnostics.

[Bug target/86775] New: Arc port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86775

Bug ID: 86775
   Summary: Arc port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: amylaar at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: arc

The Arc port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86776] New: Avr port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86776

Bug ID: 86776
   Summary: Avr port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: chertykov at gmail dot com
Blocks: 86772
  Target Milestone: ---
Target: avr

The Avr port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86777] New: Bfin port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86777

Bug ID: 86777
   Summary: Bfin port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: jiez at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: bfin

The bfin port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86778] New: c6x port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86778

Bug ID: 86778
   Summary: c6x port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: bernds at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: c6x

The C6X port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86780] New: epiphany port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86780

Bug ID: 86780
   Summary: epiphany port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: amylaar at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: epiphany

The Epiphany port needs updating for this CVE.  See the linked meta bug for
details of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86779] New: Cris port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86779

Bug ID: 86779
   Summary: Cris port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: hp at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: cris

The Cris port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86781] New: fr30 port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86781

Bug ID: 86781
   Summary: fr30 port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: nickc at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: fr30

The fr30 port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86782] New: frv port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86782

Bug ID: 86782
   Summary: frv port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: aoliva at gcc dot gnu.org, nickc at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: frv

The frv port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug tree-optimization/80155] [7/8/9 regression] Performance regression with code hoisting enabled

[prathamesh3492 at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80155

--- Comment #40 from prathamesh3492 at gcc dot gnu.org ---
ping https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80155#c38

Thanks,
Prathamesh

[Bug tree-optimization/80155] [7/8/9 regression] Performance regression with code hoisting enabled

[rguenther at suse dot de]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80155

--- Comment #41 from rguenther at suse dot de  ---
On Wed, 1 Aug 2018, prathamesh3492 at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80155
> 
> --- Comment #40 from prathamesh3492 at gcc dot gnu.org ---
> ping https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80155#c38
> 
> Thanks,
> Prathamesh

Well, all heuristics will have up and downsides.  In principle
re-ordering sinking and PRE makes sense but given it isn't
only "sinking" side-effects of this need to be watched.  I suppose
similar as to how PRE hoists code it should also sink, removing
the need of a separate (ad-hoc!) sinking pass.  Note that both
passes are confused by dead code.

But yes, in general a live-range shrinking pass is what would
improve the situation in the best possible way given the
exact situation created by PRE & friends can be created by
adjusting the testcase in source.

One complication with the idea of a live-shrinking pass is
that we have TER.  Bernd has done some kind of live-shrinking
pass before that wasn't merged.  I think I pointed you to it
at some point.

[Bug target/84521] aarch64: Frame-pointer corruption with __builtin_setjmp/__builtin_longjmp and -fomit-frame-pointer

[sudi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84521

--- Comment #28 from sudi at gcc dot gnu.org ---
Created attachment 44478
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44478&action=edit
Failing test case

As advised by James on the mailing list, I am adding the test case that is
failing on at least AAcrh64 and x86. My proposed patch fixes this on AArch64,
but I would like to add this test in the general gcc.c-torture/execute/ folder
so that other targets can also check.

[Bug target/86783] New: ft32 port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86783

Bug ID: 86783
   Summary: ft32 port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: ft32

The ft32 port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86784] New: H8 port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86784

Bug ID: 86784
   Summary: H8 port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: law at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: h8

The H8 port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86785] New: hppa port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86785

Bug ID: 86785
   Summary: hppa port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: dave.anglin at bell dot net, law at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: hppa

The hppa port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86786] New: ia64 port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86786

Bug ID: 86786
   Summary: ia64 port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: wilson at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: ia64

The ia64 port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug c++/86773] GCC accepts junk before fold expressions

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86773

Jonathan Wakely  changed:

   What|Removed |Added

   Keywords||accepts-invalid
 Status|UNCONFIRMED |NEW
   Last reconfirmed||2018-08-01
 Ever confirmed|0   |1

--- Comment #1 from Jonathan Wakely  ---
Complete testcase:

template 
auto work(Param && ...param)
{
return ("hi" ... / param);
}

int main()
{
double d = work(1.0, 2.0, 5, 4.0);
return (int)d;
}

Compiles without error. Not a regression.

[Bug target/86787] New: iq2000 port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86787

Bug ID: 86787
   Summary: iq2000 port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: nickc at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: iq2000

The iq2000 port needs updating for this CVE.  See the linked meta bug for
details of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86788] New: lm32 port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86788

Bug ID: 86788
   Summary: lm32 port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: lekernel at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: lm32

The lm32 port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug gcov-profile/35543] Add more strOp for value profiling

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35543

--- Comment #6 from Martin Liška  ---
Author: marxin
Date: Wed Aug  1 10:21:49 2018
New Revision: 263201

URL: https://gcc.gnu.org/viewcvs?rev=263201&root=gcc&view=rev
Log:
Add memmove to value profiling.

2018-08-01  Martin Liska  

PR value-prof/35543
* value-prof.c (interesting_stringop_to_profile_p):
Simplify the code and add BUILT_IN_MEMMOVE.
(gimple_stringops_transform): Likewise.
2018-08-01  Martin Liska  

PR value-prof/35543
* gcc.dg/tree-prof/val-prof-7.c: Add __builtin_memmove.

Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/tree-prof/val-prof-7.c
trunk/gcc/value-prof.c

[Bug target/86789] New: m32r port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86789

Bug ID: 86789
   Summary: m32r port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: nickc at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: m32r

The m32r port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug gcov-profile/35543] Add more strOp for value profiling

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35543

Martin Liška  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #7 from Martin Liška  ---
Closing now as fixed.

[Bug target/86790] New: m68k port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86790

Bug ID: 86790
   Summary: m68k port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: law at gcc dot gnu.org, schwab at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: m68k

The m68k port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86791] New: mcore port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86791

Bug ID: 86791
   Summary: mcore port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: nickc at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: mcore

The mcore port needs updating for this CVE.  See the linked meta bug for
details of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86792] New: microblaze port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86792

Bug ID: 86792
   Summary: microblaze port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: eager at eagercon dot com
Blocks: 86772
  Target Milestone: ---
Target: microblaze

The microblaze port needs updating for this CVE.  See the linked meta bug for
details of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86793] New: mips port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86793

Bug ID: 86793
   Summary: mips port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: mfortune at gmail dot com
Blocks: 86772
  Target Milestone: ---
Target: mips

The MIPS port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86794] New: mmix port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86794

Bug ID: 86794
   Summary: mmix port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: hp at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: mmix

The mmix port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86795] New: mn10300 port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86795

Bug ID: 86795
   Summary: mn10300 port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: aoliva at gcc dot gnu.org, law at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: mn10300

The mn10300 port needs updating for this CVE.  See the linked meta bug for
details of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86796] New: Moxie port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86796

Bug ID: 86796
   Summary: Moxie port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: green at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: moxie

The Moxie port needs updating for this CVE.  See the linked meta bug for
details of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86797] New: msp430 port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86797

Bug ID: 86797
   Summary: msp430 port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: nickc at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: msp430

The msp430 port needs updating for this CVE.  See the linked meta bug for
details of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86798] New: nds32 port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86798

Bug ID: 86798
   Summary: nds32 port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: jasonwucj at gcc dot gnu.org, shiva0217 at gmail dot com
Blocks: 86772
  Target Milestone: ---
Target: nds32

The nds32 port needs updating for this CVE.  See the linked meta bug for
details of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86799] New: nios2 port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86799

Bug ID: 86799
   Summary: nios2 port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: chunglin.tang at gmail dot com, sandra at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: nios2

The nios2 port needs updating for this CVE.  See the linked meta bug for
details of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86800] New: nvptx port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86800

Bug ID: 86800
   Summary: nvptx port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: vries at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: nvptx

The nvptx port needs updating for this CVE.  See the linked meta bug for
details of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86801] New: Powerpcspe port (may) need updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86801

Bug ID: 86801
   Summary: Powerpcspe port (may) need updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: andrewjenner at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: powerpcspe

The powerpcspe port may need updating for this CVE.  See the linked meta bug
for details of possible actions required.

Not sure if this is separate from the rs6000 port, if so then action needs to
be taken, otherwise this report can just be closed.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86802] New: riscv port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86802

Bug ID: 86802
   Summary: riscv port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: andrew at sifive dot com, kito.cheng at gmail dot com,
palmer at dabbelt dot com, wilson at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: riscv

The riscv port needs updating for this CVE.  See the linked meta bug for
details of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86803] New: rx port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86803

Bug ID: 86803
   Summary: rx port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: nickc at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: rx

The rx port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86804] New: s390 port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86804

Bug ID: 86804
   Summary: s390 port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: hpenner at de dot ibm.bom, krebbel at gcc dot gnu.org,
uweigand at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: s390

The s390 port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86805] New: sh port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86805

Bug ID: 86805
   Summary: sh port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: aoliva at gcc dot gnu.org, olegendo at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: sh

The sh port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86806] New: sparc port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86806

Bug ID: 86806
   Summary: sparc port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: davem at redhat dot com, ebotcazou at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: sparc

The sparc port needs updating for this CVE.  See the linked meta bug for
details of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86807] New: spu port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86807

Bug ID: 86807
   Summary: spu port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: dje at gcc dot gnu.org, tsmigiel at gcc dot gnu.org,
uweigand at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: spu

The spu port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86808] New: tilegx port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86808

Bug ID: 86808
   Summary: tilegx port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: walt at tilera dot com
Blocks: 86772
  Target Milestone: ---
Target: tilegx

The tilegx port needs updating for this CVE.  See the linked meta bug for
details of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86800] nvptx port needs updating for CVE-2017-5753

[vries at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86800

--- Comment #1 from Tom de Vries  ---
Hmm, at https://nvidia.custhelp.com/app/answers/detail/a_id/4610 I read:
...
NVIDIA GeForce Experience (GFE) response to CPU speculative side channel
vulnerabilities - CVE-2017-5753, CVE-2017-5715, CVE-2017-5754
Bulletin Summary

  ...

NVIDIA believes our GPU hardware is immune to the reported security issue.
...

So I think we can define this, and be done with it:
...
#undef TARGET_HAVE_SPECULATION_SAFE_VALUE
#define TARGET_HAVE_SPECULATION_SAFE_VALUE speculation_safe_value_not_needed.
...

[Bug c++/86661] [9 Regression] g++ ICE:tree check: expected tree that contains ‘decl minimal’ structure, have ‘overload’ in note_name_declared_in_class, at cp/class.c:8288

[paolo.carlini at oracle dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86661

--- Comment #3 from Paolo Carlini  ---
Note, I'm simply fixing the regression, we will still reject the testcase
without ICEing, as we always did. I'm keeping the bug open, in case somebody
wants to argue for accepting it even without -fpermissive, I'm not going to do
the required analysis any time soon, however.

[Bug target/86805] sh port needs updating for CVE-2017-5753

[olegendo at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86805

--- Comment #1 from Oleg Endo  ---
I'm not aware of any SH implementations that do speculative execution or data
access.  So I guess 

#undef TARGET_HAVE_SPECULATION_SAFE_VALUE
#define TARGET_HAVE_SPECULATION_SAFE_VALUE speculation_safe_value_not_needed.

will suffice.

[Bug c++/86661] [9 Regression] g++ ICE:tree check: expected tree that contains ‘decl minimal’ structure, have ‘overload’ in note_name_declared_in_class, at cp/class.c:8288

[paolo at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86661

--- Comment #4 from paolo at gcc dot gnu.org  ---
Author: paolo
Date: Wed Aug  1 12:09:33 2018
New Revision: 263207

URL: https://gcc.gnu.org/viewcvs?rev=263207&root=gcc&view=rev
Log:
/cp
2018-08-01  Paolo Carlini  

PR c++/86661
* class.c (note_name_declared_in_class): Use location_of in permerror
instead of DECL_SOURCE_LOCATION (for OVERLOADs).

/testsuite
2018-08-01  Paolo Carlini  

PR c++/86661
* g++.dg/lookup/name-clash12.C: New.

Added:
trunk/gcc/testsuite/g++.dg/lookup/name-clash12.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/class.c
trunk/gcc/testsuite/ChangeLog

[Bug c++/86661] g++ ICE:tree check: expected tree that contains ‘decl minimal’ structure, have ‘overload’ in note_name_declared_in_class, at cp/class.c:8288

[paolo.carlini at oracle dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86661

Paolo Carlini  changed:

   What|Removed |Added

 Status|ASSIGNED|UNCONFIRMED
   Assignee|paolo.carlini at oracle dot com|unassigned at gcc dot 
gnu.org
Summary|[9 Regression] g++ ICE:tree |g++ ICE:tree check:
   |check: expected tree that   |expected tree that contains
   |contains ‘decl minimal’ |‘decl minimal’ structure,
   |structure, have ‘overload’  |have ‘overload’ in
   |in  |note_name_declared_in_class
   |note_name_declared_in_class |, at cp/class.c:8288
   |, at cp/class.c:8288|
 Ever confirmed|1   |0

[Bug testsuite/86153] [8/9 regression] test case g++.dg/pr83239.C fails starting with r261585

[ubizjak at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86153

Uroš Bizjak  changed:

   What|Removed |Added

   Keywords|missed-optimization |
 Target|powerpc64*-*-* aarch64  |powerpc64*-*-* aarch64
   ||alpha*-*-* x86
  Component|tree-optimization   |testsuite

--- Comment #8 from Uroš Bizjak  ---
Patch at [1].

[1] https://gcc.gnu.org/ml/gcc-patches/2018-08/msg00034.html

[Bug sanitizer/86759] ThreadSanitizer: unsupported VMA range on ppc64le

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86759

Martin Liška  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2018-08-01
 Ever confirmed|0   |1

--- Comment #1 from Martin Liška  ---
Fixed on trunk in libsanitizer:
https://reviews.llvm.org/D39924

Thus libsanitizer update will fix that.

[Bug target/86809] New: tilepro port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86809

Bug ID: 86809
   Summary: tilepro port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: walt at tilera dot com
Blocks: 86772
  Target Milestone: ---
Target: tilepro

The tilepro port needs updating for this CVE.  See the linked meta bug for
details of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86810] New: v850 port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86810

Bug ID: 86810
   Summary: v850 port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: nickc at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: v850

The v850 port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86811] New: Vax port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86811

Bug ID: 86811
   Summary: Vax port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: m...@3am-software.com
Blocks: 86772
  Target Milestone: ---
Target: vax

The Vax port needs updating for this CVE.  See the linked meta bug for details
of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86812] New: visium port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86812

Bug ID: 86812
   Summary: visium port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: ebotcazou at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: visium

The visium port needs updating for this CVE.  See the linked meta bug for
details of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86813] New: xstormy16 port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86813

Bug ID: 86813
   Summary: xstormy16 port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: nickc at gcc dot gnu.org
Blocks: 86772
  Target Milestone: ---
Target: xstormy16

The xstormy16 port needs updating for this CVE.  See the linked meta bug for
details of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug target/86814] New: xtensa port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86814

Bug ID: 86814
   Summary: xtensa port needs updating for CVE-2017-5753
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: target
  Assignee: unassigned at gcc dot gnu.org
  Reporter: rearnsha at gcc dot gnu.org
CC: sterling_augustine at tensilica dot com
Blocks: 86772
  Target Milestone: ---
Target: xtensa

The xtensa port needs updating for this CVE.  See the linked meta bug for
details of possible actions required.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
[Bug 86772] [meta-bug] tracking port status for CVE-2017-5753

[Bug c++/86815] New: [ 8 regression ] ICE on valid code on armhf

[costamagnagianfranco at yahoo dot it]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86815

Bug ID: 86815
   Summary: [ 8 regression ] ICE on valid code on armhf
   Product: gcc
   Version: 8.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
  Assignee: unassigned at gcc dot gnu.org
  Reporter: costamagnagianfranco at yahoo dot it
  Target Milestone: ---

I got the ICE while compiling armhf code, I'm attaching the preprocessed source
to this bug report.

This happens with the new gcc 8.2, and it works with previous gcc-7 and also
gcc-snapshot dated 1:20180721-1

This happens while compiling hedgewars

cd
/home/locutusofborg/hedgewars-0.9.24.1-dfsg/obj-arm-linux-gnueabihf/QTfrontend
&& c++  -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG
-DQT_WIDGETS_LIB -DVIDEOREC -D__STDC_CONSTANT_MACROS
-I/home/locutusofborg/hedgewars-0.9.24.1-dfsg/misc/libphyslayer
-I/usr/include/arm-linux-gnueabihf/qt5/QtCore/5.11.1
-I/usr/include/arm-linux-gnueabihf/qt5/QtCore/5.11.1/QtCore -I/usr/include/SDL2
-I/usr/include/arm-linux-gnueabihf
-I/home/locutusofborg/hedgewars-0.9.24.1-dfsg/obj-arm-linux-gnueabihf/QTfrontend
-I/home/locutusofborg/hedgewars-0.9.24.1-dfsg/QTfrontend
-I/home/locutusofborg/hedgewars-0.9.24.1-dfsg/QTfrontend/model
-I/home/locutusofborg/hedgewars-0.9.24.1-dfsg/QTfrontend/net
-I/home/locutusofborg/hedgewars-0.9.24.1-dfsg/QTfrontend/ui
-I/home/locutusofborg/hedgewars-0.9.24.1-dfsg/QTfrontend/ui/dialog
-I/home/locutusofborg/hedgewars-0.9.24.1-dfsg/QTfrontend/ui/page
-I/home/locutusofborg/hedgewars-0.9.24.1-dfsg/QTfrontend/ui/widget
-I/home/locutusofborg/hedgewars-0.9.24.1-dfsg/QTfrontend/util
-I/home/locutusofborg/hedgewars-0.9.24.1-dfsg/QTfrontend/util/platform
-I/usr/include/lua5.1 -I/usr/local/include -isystem
/usr/include/arm-linux-gnueabihf/qt5 -isystem
/usr/include/arm-linux-gnueabihf/qt5/QtCore -isystem
/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -isystem
/usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem
/usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem
/usr/include/arm-linux-gnueabihf/qt5/QtNetwork  -g -O2
-fdebug-prefix-map=/home/locutusofborg/hedgewars-0.9.24.1-dfsg=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -fstack-protector-all -fstack-protector
-fvisibility=hidden -Wall -pipe -O2 -g -DNDEBUG   -fPIC -std=gnu++11 -o
CMakeFiles/hedgewars.dir/model/HatModel.cpp.o -c
/home/locutusofborg/hedgewars-0.9.24.1-dfsg/QTfrontend/model/HatModel.cpp
In file included from
/usr/include/arm-linux-gnueabihf/qt5/QtCore/qvariant.h:47,
 from
/usr/include/arm-linux-gnueabihf/qt5/QtCore/qabstractitemmodel.h:43,
 from
/usr/include/arm-linux-gnueabihf/qt5/QtGui/qstandarditemmodel.h:44,
 from
/usr/include/arm-linux-gnueabihf/qt5/QtGui/QStandardItemModel:1,
 from
/home/locutusofborg/hedgewars-0.9.24.1-dfsg/QTfrontend/model/HatModel.h:27,
 from
/home/locutusofborg/hedgewars-0.9.24.1-dfsg/QTfrontend/model/HatModel.cpp:24:
/usr/include/arm-linux-gnueabihf/qt5/QtCore/qmap.h:1215:25: internal compiler
error: Segmentation fault
 using QMap::remove;
 ^~
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.


compilation works with -O1, and also with gcc-7

[Bug c++/86815] [ 8 regression ] ICE on valid code on armhf

[costamagnagianfranco at yahoo dot it]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86815

--- Comment #1 from Gianfranco  ---
Created attachment 44479
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44479&action=edit
working preprocessed-source with gcc-9 snapshot

[Bug c++/86815] [ 8 regression ] ICE on valid code on armhf

[costamagnagianfranco at yahoo dot it]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86815

--- Comment #2 from Gianfranco  ---
Created attachment 44480
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44480&action=edit
preprocessed source with buggy gcc-8

[Bug c++/86815] [ 8 regression ] ICE on valid code on armhf

[ktkachov at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86815

--- Comment #3 from ktkachov at gcc dot gnu.org ---
can you please provide the output of the gcc -v command so we can see what GCC
configuration you're using

[Bug c++/86815] [ 8 regression ] ICE on valid code on armhf

[costamagnagianfranco at yahoo dot it]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86815

--- Comment #4 from Gianfranco  ---
(In reply to ktkachov from comment #3)
> can you please provide the output of the gcc -v command so we can see what
> GCC configuration you're using

Sorry! I was going to attach it, but forgot :)

gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/8/lto-wrapper
Target: arm-linux-gnueabihf
Configured with: ../src/configure -v --with-pkgversion='Debian 8.2.0-1'
--with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--program-prefix=arm-linux-gnueabihf- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-libitm
--disable-libquadmath --disable-libquadmath-support --enable-plugin
--enable-default-pie --with-system-zlib --with-target-system-zlib
--enable-objc-gc=auto --enable-multiarch --disable-sjlj-exceptions
--with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=hard --with-mode=thumb
--disable-werror --enable-checking=release --build=arm-linux-gnueabihf
--host=arm-linux-gnueabihf --target=arm-linux-gnueabihf
Thread model: posix
gcc version 8.2.0 (Debian 8.2.0-1)

[Bug target/86800] nvptx port needs updating for CVE-2017-5753

[vries at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86800

--- Comment #2 from Tom de Vries  ---
Author: vries
Date: Wed Aug  1 13:20:32 2018
New Revision: 263209

URL: https://gcc.gnu.org/viewcvs?rev=263209&root=gcc&view=rev
Log:
[nvptx] Define TARGET_HAVE_SPECULATION_SAFE_VALUE

2018-08-01  Tom de Vries  

PR target/86800
* config/nvptx/nvptx.c (TARGET_HAVE_SPECULATION_SAFE_VALUE): Define to
speculation_safe_value_not_needed.

Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/nvptx/nvptx.c

[Bug sanitizer/86759] ThreadSanitizer: unsupported VMA range on ppc64le

[jakub at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86759

--- Comment #2 from Jakub Jelinek  ---
I think we can just cherry-pick that to trunk and perhaps 8.3 too (for full
merge from libsanitizer I'd rather wait for later, say October).

[Bug target/86800] nvptx port needs updating for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86800

Richard Earnshaw  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Richard Earnshaw  ---
I'll roll this into any back-ports.

[Bug target/86772] [meta-bug] tracking port status for CVE-2017-5753

[rearnsha at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
Bug 86772 depends on bug 86800, which changed state.

Bug 86800 Summary: nvptx port needs updating for CVE-2017-5753
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86800

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

[Bug tree-optimization/86816] New: [8 Regression] ICE: SIGSEGV in tree-ssa-pre / tail_merge_optimize

[janu.gorec at interia dot pl]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86816

Bug ID: 86816
   Summary: [8 Regression] ICE: SIGSEGV in tree-ssa-pre /
tail_merge_optimize
   Product: gcc
   Version: tree-ssa
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: tree-optimization
  Assignee: unassigned at gcc dot gnu.org
  Reporter: janu.gorec at interia dot pl
  Target Milestone: ---

Created attachment 44481
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44481&action=edit
Source of minimal test case

Environment:
/home/local/gcc820/bin/g++ -v
Using built-in specs.
COLLECT_GCC=/home/local/gcc820/bin/g++
COLLECT_LTO_WRAPPER=/home/local/gcc820/libexec/gcc/x86_64-pc-linux-gnu/8.2.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-8.2.0/configure --prefix=/home/local/gcc820
--with-gmp=/home/local --with-mpfr=/home/local --with-mpc=/home/local
--enable-languages=c,c++
Thread model: posix
gcc version 8.2.0 (GCC)


Command line:
/home/local/gcc820/bin/gcc -O2 -c -Wall -Wextra ice-test.cpp


Compiler output:
during GIMPLE pass: pre
ice-test.cpp: In member function 'void Test::TestIce(Ctx&, Signal*)':
ice-test.cpp:21:6: internal compiler error: Segmentation fault
 void Test::TestIce( Ctx& ctx, Signal* sig)
  ^~~~
0xb372cf crash_signal
../../gcc-8.2.0/gcc/toplev.c:325
0xcd8a6e vn_valueize
../../gcc-8.2.0/gcc/tree-ssa-sccvn.h:258
0xcd8a6e gvn_uses_equal
../../gcc-8.2.0/gcc/tree-ssa-tail-merge.c:366
0xcdbb36 gimple_equal_p
../../gcc-8.2.0/gcc/tree-ssa-tail-merge.c:1087
0xcdbb36 find_duplicate
../../gcc-8.2.0/gcc/tree-ssa-tail-merge.c:1281
0xcdbb36 find_clusters_1
../../gcc-8.2.0/gcc/tree-ssa-tail-merge.c:1487
0xcdbb36 find_clusters
../../gcc-8.2.0/gcc/tree-ssa-tail-merge.c:1508
0xcdbb36 tail_merge_optimize(unsigned int)
../../gcc-8.2.0/gcc/tree-ssa-tail-merge.c:1752
0xc8a515 execute
../../gcc-8.2.0/gcc/tree-ssa-pre.c:4209
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See  for instructions.


Same for -O3 and gcc-8.1.0.
gcc-7.3.0 (and 6, 5, 4.9, 4.7) is Ok.


Minimal test case: (also in attachment)

class Signal
{
public:
int m_Mode;
};

class Ctx
{
public:
boolm_Invert;

voidDoSomething();
};

class Test
{
voidTestIce( Ctx& ctx, Signal* sig);
};

void Test::TestIce( Ctx& ctx, Signal* sig)
{
int invert = false;

if( ! ctx.m_Invert)
invert = ! invert;

switch( sig->m_Mode)
{
case 1:
invert = ! invert;
break;

case 2:
invert = true;
break;
}

if( invert)
ctx.DoSomething();
}

[Bug debug/63572] [6/7/8/9 Regression] ICF breaks user debugging experience

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63572

Martin Liška  changed:

   What|Removed |Added

 CC||vries at gcc dot gnu.org
   Assignee|marxin at gcc dot gnu.org  |unassigned at gcc dot 
gnu.org

--- Comment #18 from Martin Liška  ---
It's still valid, maybe Tom will be one day interested. Unassigning from me
now..

[Bug c++/86815] [ 8 regression ] ICE on valid code on armhf

[costamagnagianfranco at yahoo dot it]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86815

--- Comment #5 from Gianfranco  ---
working one:
/usr/lib/gcc-snapshot/bin/gcc -v
Using built-in specs.
COLLECT_GCC=/usr/lib/gcc-snapshot/bin/gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc-snapshot/libexec/gcc/arm-linux-gnueabihf/9/lto-wrapper
Target: arm-linux-gnueabihf
Configured with: ../src/configure -v --with-pkgversion='Debian 20180721-1'
--with-bugurl=file:///usr/share/doc/gcc-snapshot/README.Bugs
--enable-languages=c,ada,c++,go,fortran,objc,obj-c++
--prefix=/usr/lib/gcc-snapshot --with-gcc-major-version-only --program-prefix=
--enable-shared --enable-linker-build-id --disable-nls --with-sysroot=/
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-libitm
--disable-libquadmath --disable-libquadmath-support --enable-plugin
--with-system-zlib --enable-objc-gc=auto --enable-multiarch
--disable-sjlj-exceptions --with-arch=armv7-a --with-fpu=vfpv3-d16
--with-float=hard --with-mode=thumb --disable-werror --enable-checking=yes
--build=arm-linux-gnueabihf --host=arm-linux-gnueabihf
--target=arm-linux-gnueabihf
Thread model: posix
gcc version 9.0.0 20180721 (experimental) [trunk revision 262917] (Debian
20180721-1)

[Bug gcov-profile/83877] Make gcov accept a path to the gcda and a path to the gcno file

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83877

Martin Liška  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |WONTFIX

--- Comment #2 from Martin Liška  ---
Well, note that gcov accepts multiple files. So it does not makes much sense to
provide path to gcda files. But you can definitely use:

$ gcov test.cpp -o myroot
myroot/test.gcno:cannot open notes file

That will start search starting from a specific folder.

[Bug gcov-profile/28564] gcov fails to store the absolute path to the source files

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28564

Martin Liška  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |WONTFIX

--- Comment #4 from Martin Liška  ---
Well after reconsidering this, I probably don't want to hardwire absolute paths
to .gcda and .gcno files. One can do instrumentation and run on a different
machine, thus usage of -o option is right thing to do.

[Bug gcov-profile/86817] New: [8/9 Regression] Misleading warning in gcov since r254672

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86817

Bug ID: 86817
   Summary: [8/9 Regression] Misleading warning in gcov since
r254672
   Product: gcc
   Version: 9.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: gcov-profile
  Assignee: unassigned at gcc dot gnu.org
  Reporter: marxin at gcc dot gnu.org
CC: marxin at gcc dot gnu.org
  Target Milestone: ---

When gcov is run for 2 files one can see:

$ rm *.gc* ; gcc --coverage main.c && ./a.out && gcc --coverage main2.c &&
./a.out && gcov main.c main2.c
main2.gcno:'main' has arcs to entry block
main2.gcno:'main' has arcs from exit block
File 'main.c'
Lines executed:100.00% of 2
Creating 'main.c.gcov'

File 'main2.c'
Lines executed:100.00% of 2
Creating 'main2.c.gcov'

Which is obviously wrong.

[Bug gcov-profile/86817] [8/9 Regression] Misleading warning in gcov since r254672

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86817

Martin Liška  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
   Last reconfirmed||2018-08-01
   Assignee|unassigned at gcc dot gnu.org  |marxin at gcc dot 
gnu.org
   Target Milestone|--- |8.3
 Ever confirmed|0   |1

[Bug libstdc++/60555] std::system_category().default_error_condition() doesn't map system errno values to std::generic_category()

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60555

--- Comment #10 from Jonathan Wakely  ---
Author: redi
Date: Wed Aug  1 13:57:05 2018
New Revision: 263210

URL: https://gcc.gnu.org/viewcvs?rev=263210&root=gcc&view=rev
Log:
PR libstdc++/60555 std::system_category() should recognise POSIX errno values

PR libstdc++/60555
* src/c++11/system_error.cc
(system_error_category::default_error_condition): New override to
check for POSIX errno values.
* testsuite/19_diagnostics/error_category/generic_category.cc: New
* testsuite/19_diagnostics/error_category/system_category.cc: New
test.

Added:
   
trunk/libstdc++-v3/testsuite/19_diagnostics/error_category/generic_category.cc
   
trunk/libstdc++-v3/testsuite/19_diagnostics/error_category/system_category.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/src/c++11/system_error.cc

[Bug c++/86469] Dwarf Error: Offset (1678049557) greater than or equal to .debug_str size (5846).

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86469

Richard Biener  changed:

   What|Removed |Added

 Status|WAITING |RESOLVED
   See Also||https://sourceware.org/bugz
   ||illa/show_bug.cgi?id=23425
 Resolution|--- |MOVED

--- Comment #17 from Richard Biener  ---
Moved to sourceware.

[Bug libstdc++/60555] std::system_category().default_error_condition() doesn't map system errno values to std::generic_category()

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60555

Jonathan Wakely  changed:

   What|Removed |Added

   Last reconfirmed|2014-03-18 00:00:00 |2018-8-1

--- Comment #11 from Jonathan Wakely  ---
Fixed on trunk so far.