https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85689
W E Brown changed:
What|Removed |Added
CC||webrown.cpp at gmail dot com
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84923
--- Comment #7 from Vladimir Mezentsev
---
About comment #3 and #4.
I cannot reproduce a problem.
Is it a cross compilation on x86 for aarch64 ?
What need to do to reproduce the problem ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85646
--- Comment #4 from Jason Merrill ---
Author: jason
Date: Tue May 8 03:13:09 2018
New Revision: 260022
URL: https://gcc.gnu.org/viewcvs?rev=260022=gcc=rev
Log:
PR c++/85646 - lambda visibility.
* decl2.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85619
Martin Sebor changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85619
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85623
Martin Sebor changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85623
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85643
Martin Sebor changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85643
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85650
Martin Sebor changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85650
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84890
--- Comment #9 from Martin Sebor ---
(In reply to Martin Sebor from comment #8)
To clarify: it's not correct to directly include the header in a GCC
source file. Instead, one is expected to define the INCLUDE_STRING macro
before including
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85652
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85691
Bug ID: 85691
Summary: Faulty Class Member Default Initialization - No
Warning or Error
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85687
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85646
--- Comment #3 from Jason Merrill ---
Author: jason
Date: Mon May 7 23:50:16 2018
New Revision: 260017
URL: https://gcc.gnu.org/viewcvs?rev=260017=gcc=rev
Log:
PR c++/85646 - lambda visibility.
* decl2.c
I spent a while tweaking the visibility code while I was working on
the lambdas in templates overhaul, but ended up putting that aside.
This PR led me to pull that out again, but I hadn't realized that some
of the code I was messing with was only a year old, from Nathan's fix
for c++/79296.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85690
Bug ID: 85690
Summary: missing suggested header for std-qualified names
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66812
Eric Gallager changed:
What|Removed |Added
Keywords||patch
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84890
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66811
Eric Gallager changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66627
Bug 66627 depends on bug 66783, which changed state.
Bug 66783 Summary: No error-checking for creating structs containing opaque
structs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66783
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66783
Eric Gallager changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66594
Eric Gallager changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
As prophesied by gcc 8.1, I have nuked the ARM-era for-scope
compatibilty of -fno-for-scope. It has been a c++98-only feature, and
that's not the default anymore. Time for this to go.
nathan
--
Nathan Sidwell
2018-05-07 Nathan Sidwell
gcc/cp/
Remove fno-for-scope
*
On Tue, May 01, 2018 at 10:07:05PM +0200, Thomas Koenig wrote:
>
> Index: gcc/fortran/simplify.c
> ===
> --- gcc/fortran/simplify.c(Revision 259683)
> +++ gcc/fortran/simplify.c(Arbeitskopie)
> @@ -32,7 +32,7 @@ along with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85651
Martin Sebor changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85651
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85593
--- Comment #7 from Austin Morton ---
I will certainly give writing a patch a try - but I will disclaim up front that
because there is a viable workaround for the issue I was having (patch below
[1]), this issue is "resolved" as far as my
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85687
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85686
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85665
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85316
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78947
Andrew Pinski changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85559
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66627
David Malcolm changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85680
--- Comment #3 from Mathias Stearn ---
MSVC and ICC both also handle this poorly: https://godbolt.org/g/i4wMYa
https://developercommunity.visualstudio.com/content/problem/246786/poor-codegen-for-value-init-followed-by-explicit-i.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58801
Eric Gallager changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85683
--- Comment #4 from Jakub Jelinek ---
This seems to work.
--- gcc/config/i386/i386.md.jj 2018-05-02 23:55:44.0 +0200
+++ gcc/config/i386/i386.md 2018-05-07 22:27:18.848705146 +0200
@@ -19285,6 +19285,40 @@
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85675
--- Comment #2 from Harald Anlauf ---
Running under the debugger (separate file 2 only):
Breakpoint 1, gfc_omp_predetermined_sharing (decl=0xb7c100fc)
at ../../trunk/gcc/fortran/trans-openmp.c:152
152 if (VAR_P (decl) && TREE_READONLY
GCC maintainers:
The architecture independent builtin __builtin_prefetch() is defined
as:
void __builtin_prefetch (const void *addr, int n1, int n2)
n1 -
prefetch read = 0, prefetch write = 1
n2 - temporal locality 0 to 3. No
temporal locality = 0, high temporal
locality = 3.
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54664
Eric Gallager changed:
What|Removed |Added
Keywords||build
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85685
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55143
Eric Gallager changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47093
Bug 47093 depends on bug 55143, which changed state.
Bug 55143 Summary: vms-c.o:(.toc+0x0): undefined reference to
`c_default_pointer_mode' (building cc1plus)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55143
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47093
Bug 47093 depends on bug 48904, which changed state.
Bug 48904 Summary: x86_64-knetbsd-gnu fails to build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48904
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48904
Eric Gallager changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
Hi
Here is the patch to add backtrace info to debug assertion failure
output.
Example:
/home/fdt/dev/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/debug/vector:188:
In function:
std::__debug::vector<_Tp, _Allocator>::vector(_InputIterator,
_InputIterator, const _Allocator&)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25914
--- Comment #7 from dave.anglin at bell dot net ---
On 2018-05-07 4:05 PM, egallager at gcc dot gnu.org wrote:
> Did this proposal ever happen?
Yes:
http://pubs.opengroup.org/onlinepubs/9699919799/functions/psignal.html
Hi
This is to fix what is reported as the pretty function in case of
debug assertion failure in the range constructor.
Result looks like this:
/home/fdt/dev/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/debug/vector:188:
In function:
std::__debug::vector<_Tp,
Hi
Here is the 1st patch of a series to improve Debug Mode feedback.
This patch add the content of __PRETTY_FUNCTION__ in the debug
assertion output.
Tested under Linux x86_64.
I'll commit tomorrow if not told otherwise.
* include/debug/formatter.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47098
Eric Gallager changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85675
Harald Anlauf changed:
What|Removed |Added
CC||anlauf at gmx dot de
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47093
Bug 47093 depends on bug 47098, which changed state.
Bug 47098 Summary: i686-openbsd3.0: OBSD_LIB_SPEC missing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47098
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44756
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49656
Eric Gallager changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37759
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25914
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32815
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85689
Bug ID: 85689
Summary: if constexpr compiles false branch
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
On 01/05/18 15:34 +0100, Jonathan Wakely wrote:
On 12/03/18 16:02 -0300, Tulio Magno Quites Machado Filho wrote:
Changes since v1:
- Completely rewrite of the patch to set ENABLE_FLOAT128 at libstdc++
build time and undef _GLIBCXX_USE_FLOAT128 when building user code.
--- 8< ---
In order to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85683
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85688
--- Comment #1 from Jonathan Wakely ---
If this is accepted as a bug then I'll create a similar one for the C front
end:
gcc -c -x c - -mno-float128 <<< 'void f() { __float128 f = 0.0; }'
: In function ‘f’:
:1:12: error: unknown type name
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85688
Bug ID: 85688
Summary: Unhelpful fix-it hint for __float128 when using
-mno-float128
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Keywords: diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85683
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85593
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
Known
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82922
Eric Gallager changed:
What|Removed |Added
CC||david at westcontrol dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85676
Eric Gallager changed:
What|Removed |Added
Keywords||diagnostic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #10 from Jonathan Wakely ---
Created attachment 44083
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44083=edit
Restore previous behaviour of #undef _GLIBCXX_USE_FLOAT128 based on configure
checks.
This still follows the same
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85618
Jason Merrill changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85618
--- Comment #4 from Jason Merrill ---
Author: jason
Date: Mon May 7 19:34:59 2018
New Revision: 260013
URL: https://gcc.gnu.org/viewcvs?rev=260013=gcc=rev
Log:
PR c++/85618 - ICE with initialized VLA.
* tree.c (vla_type_p):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71769
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85618
--- Comment #3 from Jason Merrill ---
Author: jason
Date: Mon May 7 19:22:35 2018
New Revision: 260012
URL: https://gcc.gnu.org/viewcvs?rev=260012=gcc=rev
Log:
PR c++/85618 - ICE with initialized VLA.
* tree.c (vla_type_p):
The fix for 84560 clarified that an array with multiple non-constant
bounds is not an N3639 array of runtime bound, because that proposal
only allowed a single variable bound. But store_init_value was using
array_of_runtime_bound_p to decide whether we need to use
build_vec_init for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80506
--- Comment #12 from emsr at gcc dot gnu.org ---
Yes, all other stuff is rolled back except for this patch.
* doc/xml/manual/using.xml (table.cmd_options): Document that the
C++17 Filesystem implementation also needs -lstdc++fs.
Committed to trunk.
commit c12f73eb5111b4a1f4c8cc19e3875bd2e20390d4
Author: Jonathan Wakely
Date: Mon May 7 20:13:17 2018 +0100
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80506
--- Comment #11 from emsr at gcc dot gnu.org ---
Yes, I had an ugly morning with svn.
Hopefully the bits are rolled back.
That chunk is 83140.
Ed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #9 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #8)
> The new logic [...] comes before the automatically added parts.
And obviously you can't #undef something that hasn't been defined yet.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
Jonathan Wakely changed:
What|Removed |Added
Keywords||build
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #8 from Jonathan Wakely ---
(In reply to Marc Glisse from comment #7)
> Yes, or maybe don't generate #define _GLIBCXX_USE_FLOAT128 0 but instead /*
> #undef _GLIBCXX_USE_FLOAT128 */ as we used to do and as the rest of the
>
gd【袋-【开---税】--票】-电话:136-4072-5689
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85323
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85680
--- Comment #2 from Mathias Stearn ---
FYI, I don't think this is a signed/unsigned thing since it also repros with
unsigned long https://godbolt.org/g/LTmrpi
My initial repo actually used size_t, but I (incorrectly) changed it to long
rather
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85671
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85687
Bug ID: 85687
Summary: ICE in gfc_sym_identifier, at fortran/trans-decl.c:351
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85686
Bug ID: 85686
Summary: [8/9 Regression] ICE in gfc_conv_scalarized_array_ref,
at fortran/trans-array.c:3385
Product: gcc
Version: 9.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85685
Bug ID: 85685
Summary: [7/8/9 Regression] ICE in
gfc_deallocate_scalar_with_status, at
fortran/trans.c:1598
Product: gcc
Version: 9.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80506
--- Comment #10 from Jonathan Wakely ---
(In reply to emsr from comment #5)
> Author: emsr
> Date: Mon May 7 15:55:11 2018
> New Revision: 260001
>
> URL: https://gcc.gnu.org/viewcvs?rev=260001=gcc=rev
> Log:
> 2018-05-07 Edward Smith-Rowland
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85671
--- Comment #3 from Jonathan Wakely ---
Author: redi
Date: Mon May 7 17:26:28 2018
New Revision: 260009
URL: https://gcc.gnu.org/viewcvs?rev=260009=gcc=rev
Log:
PR libstdc++/85671 allow copy elision in path concatenation
By performing the /=
By performing the /= operation on a named local variable instead of a
temporary the copy made for the return value can be elided.
PR libstdc++/85671
* include/bits/fs_path.h (operator/): Permit copy elision.
* include/experimental/bits/fs_path.h (operator/): Likewise.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85680
--- Comment #1 from Marc Glisse ---
Quite impressive how we do the test in multiple ways, which are not quite
equivalent because of the wrapping semantics of unsigned. Maybe if we asserted
that the argument of operator new must be less than the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85681
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85681
--- Comment #7 from Steve Kargl ---
On Mon, May 07, 2018 at 05:01:59PM +, luis.machado at linaro dot org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85681
>
> --- Comment #6 from Luis Machado ---
> Would you please confirm the
[Trying to get some feedback. I earlier posted on gcc-help a week ago]
In tree.def -
/* Minimum and maximum values. When used with floating point, if both
operands are zeros, or if either operand is NaN, then it is unspecified
which of the two operands is returned as the result. */
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85681
--- Comment #6 from Luis Machado ---
Would you please confirm the bootstrap is back to normal and declare it
resolved? I don't have permission to change its state.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80506
--- Comment #9 from emsr at gcc dot gnu.org ---
Author: emsr
Date: Mon May 7 16:59:08 2018
New Revision: 260008
URL: https://gcc.gnu.org/viewcvs?rev=260008=gcc=rev
Log:
2018-05-07 Edward Smith-Rowland <3dw...@verizon.net>
Moar PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85616
--- Comment #4 from Denis Roux ---
I agree that the given example code is breaking the C strict aliasing rule.
However, I do not believe that the issue I'm reporting is related to aliasing.
Further more, adding -fno-strict-aliasing option do not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85683
Alexander Monakov changed:
What|Removed |Added
Keywords||missed-optimization
All,
We were using a different convention for P_l^m assoc_legendre(int l, int
m, FloatTp x)
- the so-called Condon-Shortley convention which includes (-1)^m.
This unfortunately is common.
This factor is taken out to match the standard. The underlying __detail
code has an arg that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85646
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
1 - 100 of 162 matches
Mail list logo