-pc-linux-gnu/8.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-source-trunk/configure --enable-languages=c,c++,lto
--prefix=/home/su/software/tmp/gcc/gcc-trunk --disable-bootstrap
Thread model: posix
gcc version 8.0.0 20171026 (experimental) [trunk revision 254125] (GCC
+Cc gcc-list.
Does any gcc developer have any comments?
On Mon, Sep 25, 2017 at 01:41:55PM -0700, Myriachan wrote:
> This question that "supercat" posted on Stack Overflow ran into an
> interesting problem:
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82734
--- Comment #1 from Andrew Pinski ---
Why can't you use std::remove_cv here?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59515
--- Comment #3 from Andrew Pinski ---
Maybe -fkeep-inline-functions ?
On Thu, Oct 26, 2017 at 10:12 AM, Wilco Dijkstra wrote:
> GCC's default optimization level is -O0. Unfortunately unlike other
> compilers,
> GCC generates extremely inefficient code with -O0. It is almost unusable for
> low-level debugging or manual inspection of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81797
--- Comment #44 from Chris Johns ---
(In reply to Jonathan Wakely from comment #42)
> I think something else is going on here, and not a race condition in the
> makefile.
I agree. I see the failure after a few files have been built.
>
> This
On Tue, Oct 24, 2017 at 3:10 PM, Ian Lance Taylor wrote:
> I merged trunk revision 254059 to the gccgo branch.
I've now merged trunk revision 254126.
Ian
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29600
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
---
On 10/21/2017 11:17 AM, Bernhard Reutner-Fischer wrote:
> On 21 October 2017 at 02:26, Damian Rouson
> wrote:
>>
>> Hi Richard,
>>
>> Attached is a revised patch that makes the downloading of Fortran
>> prerequisites optional via a new --no-fortran flag that can be
On Wed, Oct 25, 2017 at 07:57:09PM -0400, Michael Meissner wrote:
> On Wed, Oct 25, 2017 at 11:41:24PM +, Joseph Myers wrote:
> > My only comment on this version is that the documentation in cpp.texi of
> > __FP_FAST_* should be updated to mention __FP_FAST_FMAF@var{n} and
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82081
Jonathan Wakely changed:
What|Removed |Added
Status|RESOLVED|NEW
Resolution|INVALID
Hi,
On Wed, Oct 25, 2017 at 10:26:46AM -0500, Will Schmidt wrote:
> 2017-10-25 Will Schmidt
>
> * gcc.target/powerpc/fold-vec-neg-char.c: New.
> * gcc.target/powerpc/fold-vec-neg-floatdouble.c: New.
> * gcc.target/powerpc/fold-vec-neg-int.c: New.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81028
Alexander Cherepanov changed:
What|Removed |Added
CC||ch3root at openwall dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82081
--- Comment #5 from Paweł Dziepak ---
Is it really undefined? n4700 states in 18.4/5:
Whenever an exception is thrown and the search for a handler (18.3) encounters
the outermost block of a function with a non-throwing exception specification,
LWG 2133 makes it a requirement for some of the algorithms to protect
against overlaoded comma operators. This does so, and adapts some
tests to verify it, using our iterator wrappers. Those wrappers have a
member oeprator, but that only handles the case where the iterator is
the left operand, so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82081
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82081
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
On 10/26/2017 11:52 AM, Richard Sandiford wrote:
Martin Sebor writes:
/* The tree and const_tree overload templates. */
namespace wi
{
+ class unextended_tree
+ {
+ private:
+const_tree m_t;
+
+ public:
+unextended_tree () {}
Defining no-op ctors is quite
Hi Will,
On Thu, Oct 26, 2017 at 05:13:38PM -0500, Will Schmidt wrote:
> * config/rs6000/rs6000.c: (rs6000_gimple_fold_builtin) Add support for
> gimple folding of vec_madd() intrinsics.
The colon goes after the closing parenthesis, and continuation lines
should not have extra
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82741
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82081
Andrew Pinski changed:
What|Removed |Added
CC||pdziepak at quarnos dot org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82741
Bug ID: 82741
Summary: Optimisations may cause noexcept specifier to be
ignored
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
On 10/26/2017 01:17 PM, Pedro Alves wrote:
On 10/26/2017 07:54 PM, Martin Sebor wrote:
(...) in the general case, it is preferable to
declare each variable at the point where its initial value is known
(or can be computed) and initialize it on its declaration.
With that I fully agree, except
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82683
--- Comment #11 from Steve Ellcey ---
I think I see where this is going wrong but I don't know what to do about it.
In try_combine, line 3288 we have i2 and i3 of:
(insn 18 16 19 3 (set (reg:DI 91)
(ashift:DI (reg:DI 83 [ _26 ])
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82740
Bug ID: 82740
Summary: [concepts] requires clause evaluated early
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
This patch adds an explicit conversion between type aliases.
Otherwise we can get a crash in the backend when GCC sees a
fold_convert_loc between two record types that the GCC backend appear
to be different. Adding the explicit conversion will insert a
VIEW_CONVERT_EXPR where needed. The test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82683
--- Comment #10 from Segher Boessenkool ---
reg-notes.def says
/* The value in REG dies in this insn (i.e., it is not needed past
this insn). If REG is set in this insn, the REG_DEAD note may,
but need not, be omitted. */
REG_NOTE
Snapshot gcc-7-20171026 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20171026/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7
Hi,
[PATCH, rs6000] (v2) Gimple folding for vec_madd()
Add support for gimple folding of the vec_madd() (vector multiply-add)
intrinsics. Per earlier feedback and education, this now includes
the addition of a "define_expand fmav8hi4" in altivec.md.
Testcase coverage is provided by
On Thu, 2017-10-26 at 11:38 +0200, Richard Biener wrote:
> You can eventually keep the option, marking it as Ignore (like we do
> for options we remove but "keep" for backward compatibility). The
> diagnostic (as warning, given the option will be just ignored) could
> be emited from option
Hi Carl,
On Mon, Oct 23, 2017 at 08:36:03AM -0700, Carl Love wrote:
> The mode attribute wd will not work
> for the define expand as the V16QI maps to "b" not "q". So I do need to
> have VSX_XXBR.
Why is that a problem? Why do you want to swap the order of the whole
vector instead of changing
Hi!
The following testcase is miscompiled, because due to STV we end up
with a load from V2DFmode MEM for which get_pool_entry returns
a V1TImode vector. maybe_get_pool_constant doesn't have code
to handle mode differences between what get_pool_constant returns
and the requested mode. While it
On Thu, 2017-10-26 at 12:35 -0600, Sandra Loosemore wrote:
> On 10/26/2017 11:47 AM, Gerald Pfeifer wrote:
> > Thanks you for fleshing this out, Jim!
> >
> > This looks fine to me (modula Sandra's note). Just a question:
> > would
> > we refer to GDB instead of gdb here? It feels a little in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82739
Bug ID: 82739
Summary: Sort is 30% slower compared to gcc44 on presorted
array
Product: gcc
Version: 7.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82471
--- Comment #10 from Thomas Koenig ---
Created attachment 42482
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42482=edit
Here's a first attempt...
I've committed this patch, intended for bare-metal nios2-elf targets
with custom linker scripts. In conjunction with section attributes, it
provides a way to tell GCC that an object is assigned to the low or high
32K memory regions so that it can be addressed via a signed 16-bit
offset from
I've committed this patch, which allows users to specify additional data
sections (beyond the normal small-data sections) where GP-relative
addressing can be used. It's intended for use on bare-metal nios2-elf
targets in conjunction with section attributes and a custom linker script.
-Sandra
old transitions found (bb 64)
+===GNAT BUG DETECTED==+
| 8.0.0 20171026 (experimental) [trunk revision 254096] (x86_64-suse-linux)
GCC error:|
| verify_flow_info failed |
It's the RTL basic block reorder
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82709
--- Comment #2 from harper at msor dot vuw.ac.nz ---
Apologies - I did not find bug 40196 when I was looking for possible
duplicates of my bug 82709.
On Tue, 24 Oct 2017, dominiq at lps dot ens.fr wrote:
> Date: Tue, 24 Oct 2017 23:51:55 +
On 26/10/17 21:37 +0100, Jonathan Wakely wrote:
On 26/10/17 21:30 +0100, Jonathan Wakely wrote:
On 26/10/17 22:19 +0200, François Dumont wrote:
@@ -1232,7 +1232,7 @@ class Printer(object):
# Add a name using _GLIBCXX_BEGIN_NAMESPACE_CONTAINER.
def add_container(self, base, name, function):
On 26/10/17 21:30 +0100, Jonathan Wakely wrote:
On 26/10/17 22:19 +0200, François Dumont wrote:
@@ -1232,7 +1232,7 @@ class Printer(object):
# Add a name using _GLIBCXX_BEGIN_NAMESPACE_CONTAINER.
def add_container(self, base, name, function):
self.add_version(base, name, function)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82692
Uroš Bizjak changed:
What|Removed |Added
Attachment #42479|0 |1
is obsolete|
On 26/10/17 22:19 +0200, François Dumont wrote:
@@ -1232,7 +1232,7 @@ class Printer(object):
# Add a name using _GLIBCXX_BEGIN_NAMESPACE_CONTAINER.
def add_container(self, base, name, function):
self.add_version(base, name, function)
-self.add_version(base +
On 26/10/17 21:45 +0200, François Dumont wrote:
On 26/10/2017 19:09, Jonathan Wakely wrote:
On 26/10/17 18:55 +0200, Daniel Krügler wrote:
2017-10-26 7:51 GMT+02:00 François Dumont :
Hi
We once talk about rename the __cxx1998 namespace into
something less
C++98
Hi
When restoring versioned namespace feature I forgot to check for
the pretty printer tests which are now broken.
Here is the patch to fix those. Tested under Linux x86_64 normal
and versioned namepace modes, ok to commit ?
François
diff --git
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82707
Tom de Vries changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82707
--- Comment #12 from Tom de Vries ---
Author: vries
Date: Thu Oct 26 20:09:24 2017
New Revision: 254120
URL: https://gcc.gnu.org/viewcvs?rev=254120=gcc=rev
Log:
Fix unsharing of GIMPLE_OMP_{SINGLE,TARGET,TEAMS} in gimple_copy
2017-10-26 Tom
On 26.10.2017 21:43, Kamil Rytarowski wrote:
> Tested on:
>
> $ uname -rms
> NetBSD 8.99.4 amd64
>
I forgot to amend everything in this patch, will fix in -v3.
signature.asc
Description: OpenPGP digital signature
Tested on:
$ uname -rms
NetBSD 8.99.4 amd64
The NetBSD support has been developed directly in the compiler-rt upstream
source.
Testing against the LLVM+Clang+compiler-rt (2017-10-25 snapshot from HEAD):
$ make check-asan
Failing Tests (2):
AddressSanitizer-Unit ::
Tested on:
$ uname -rms
NetBSD 8.99.4 amd64
The NetBSD support has been developed directly in the compiler-rt upstream
source.
Testing against the LLVM+Clang+compiler-rt (2017-10-25 snapshot from HEAD):
$ make check-asan
Failing Tests (2):
AddressSanitizer-Unit ::
On Thu, Oct 26, 2017 at 05:12:40PM +, Wilco Dijkstra wrote:
> GCC's default optimization level is -O0. Unfortunately unlike other
> compilers,
> GCC generates extremely inefficient code with -O0. It is almost unusable for
> low-level debugging or manual inspection of generated code. So a
> GCC's default optimization level is -O0. Unfortunately unlike other
> compilers, GCC generates extremely inefficient code with -O0.
Agreed (but this can probably be worked on).
> It is almost unusable for low-level debugging or manual inspection of
> generated code.
Likewise.
> So a -O
On 26/10/2017 19:09, Jonathan Wakely wrote:
On 26/10/17 18:55 +0200, Daniel Krügler wrote:
2017-10-26 7:51 GMT+02:00 François Dumont :
Hi
We once talk about rename the __cxx1998 namespace into something
less
C++98 biased. Here is the patch to do so.
Ok with
On Thu, Oct 26, 2017 at 02:43:55PM +0200, Richard Biener wrote:
> On Thu, Oct 26, 2017 at 2:18 PM, Richard Sandiford
> wrote:
> > Richard Biener writes:
> >> On Mon, Oct 23, 2017 at 1:22 PM, Richard Sandiford
> >>
Richard Biener writes:
> On Thu, Oct 26, 2017 at 2:18 PM, Richard Sandiford
> wrote:
>> Richard Biener writes:
>>> On Mon, Oct 23, 2017 at 1:22 PM, Richard Sandiford
>>> wrote:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82738
Bug ID: 82738
Summary: [meta-bug] issues with the -Og optimization level
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
> Can you figure what oldest GCC release supports the C++11/14 POD handling
> that would be required?
GCC needs to be buildable by other compilers than itself though.
--
Eric Botcazou
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82735
--- Comment #3 from Marc Glisse ---
Actually, what CSE1 does might be fine, and it is LRA that should have noticed
that the register it assigned was clobbered, so it should have spilled (or
better rematerialized). Assuming the i386 backend does
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82735
Marc Glisse changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
On Thu, Oct 26, 2017 at 09:24:58PM +0200, Kamil Rytarowski wrote:
> On 26.10.2017 21:19, Jakub Jelinek wrote:
> > On Thu, Oct 26, 2017 at 09:02:25PM +0200, Kamil Rytarowski wrote:
> >> 2017-10-26 Kamil Rytarowski
> >>
> >>* sanitizer_common/Makefile.am
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58687
--- Comment #35 from Max TenEyck Woodbury ---
True, none of the specifically listed maintainers have commented on
this version of the patch. There are three people listed and a
general reference to all C and C++ front end maintainers. It is
On 26.10.2017 21:19, Jakub Jelinek wrote:
> On Thu, Oct 26, 2017 at 09:02:25PM +0200, Kamil Rytarowski wrote:
>> 2017-10-26 Kamil Rytarowski
>>
>> * sanitizer_common/Makefile.am (sanitizer_common_files): Add
>> sanitizer_platform_limits_netbsd.cc.
>> *
Hi Paul,
Without having tested the patch, it looks reasonable to me. So ok from my side.
- Andre
Am 26. Oktober 2017 21:12:45 MESZ schrieb Paul Richard Thomas
:
>Dear All,
>
>Thanks to Dimitry Liakh for both reporting the problem and doing a lot
>of the
On Thu, Oct 26, 2017 at 09:02:25PM +0200, Kamil Rytarowski wrote:
> 2017-10-26 Kamil Rytarowski
>
> * sanitizer_common/Makefile.am (sanitizer_common_files): Add
> sanitizer_platform_limits_netbsd.cc.
> * sanitizer_common/Makefile.in: Regenerated.
Why is this
On 10/26/2017 07:54 PM, Martin Sebor wrote:
> (...) in the general case, it is preferable to
> declare each variable at the point where its initial value is known
> (or can be computed) and initialize it on its declaration.
With that I fully agree, except it's not always possible or
natural.
2017-10-26 Kamil Rytarowski
* sanitizer_common/Makefile.am (sanitizer_common_files): Add
sanitizer_platform_limits_netbsd.cc.
* sanitizer_common/Makefile.in: Regenerated.
---
libsanitizer/ChangeLog| 6 ++
Dear All,
Thanks to Dimitry Liakh for both reporting the problem and doing a lot
of the diagnostic work. Once the offending line in a very complicated
code was located, the fix was trivial. Generating a reduced testcase
took rather longer :-)
The comment in the testcase tells the story. The fix
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67224
spoa at eircom dot net changed:
What|Removed |Added
CC||spoa at eircom dot net
---
On 10/26/2017 12:05 PM, Pedro Alves wrote:
On 10/26/2017 05:37 PM, Martin Sebor wrote:
I agree that the latter use case is more common in GCC, but I don't
see it as a good thing. GCC was written in C and most code still
uses now outdated C practices such as declaring variables at the top
of a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82737
Matti Bryce changed:
What|Removed |Added
Target||x86_64-w64-mingw32
URL|
On 10/26/2017 11:47 AM, Gerald Pfeifer wrote:
On Wed, 25 Oct 2017, Jim Wilson wrote:
The current documentation doesn't explain what the option is for, or
how one might use it. The attached patch expands the documentation a
bit to try to explain this.
OK?
Thanks you for fleshing this out,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82737
Bug ID: 82737
Summary: Compiler segfault on compilation of a certain file
(full cause unknown) (file too large for upload, link
provided)
Product: gcc
Version:
On 10/26/2017 02:12 PM, Eric Gallager wrote:
On 10/26/17, Nathan Sidwell wrote:
On 10/26/2017 10:34 AM, David Malcolm wrote:
Possibly a silly question, but is it OK to have a formatted string
call in which some of the arguments aren't consumed? (here "col" is only
consumed
While poring over the Transport Tycoon Deluxe disassembly, commonly
known to have been hand-written in assembler, I stumbled across this
tidbit, which I think is kinda neat:
004057F7 83 7D B8 01 cmp dword ptr [ebp-48h],1
004057FB 1B C0sbb eax,eax
004057FD
Hello Olga, Sebastian,
On 20 Oct 08:36, Peryt, Sebastian wrote:
> Hi,
>
> This patch written by Olga Makhotina adds listed below missing intrinsics:
> _mm512_[mask_]cmpeq_[pd|ps]_mask
> _mm512_[mask_]cmple_[pd|ps]_mask
> _mm512_[mask_]cmplt_[pd|ps]_mask
> _mm512_[mask_]cmpneq_[pd|ps]_mask
>
On 10/26/17, Wilco Dijkstra wrote:
> GCC's default optimization level is -O0. Unfortunately unlike other
> compilers,
> GCC generates extremely inefficient code with -O0. It is almost unusable
> for
> low-level debugging or manual inspection of generated code. So a -O
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758
--- Comment #21 from DIL ---
Greatly appreciate!
On 10/26/17, Nathan Sidwell wrote:
> On 10/26/2017 10:34 AM, David Malcolm wrote:
>> [CCing Rainer and Mike for the gcc-dg.exp part]
>
>> Alternate idea: could show_column become a tri-state:
>>* default: show non-zero columns
>>* never: never show columns
>>* always:
On October 26, 2017 6:50:15 PM GMT+02:00, Jeff Law wrote:
>On 10/26/2017 03:24 AM, Richard Biener wrote:
>> On Tue, Oct 24, 2017 at 8:44 PM, Jeff Law wrote:
>>> This is similar to the introduction of the ssa_propagate_engine, but
>for
>>> the
On October 26, 2017 6:47:59 PM GMT+02:00, "Bin.Cheng"
wrote:
>Hi,
>I am looking into DSE transformation of some fortran codes. Given
>below fortran declarations:
>
> real*8 a(len) , b(len) , c(len) , d(len)
> common /area/ a, b, c, d
> real*8
On 10/26/2017 05:37 PM, Martin Sebor wrote:
> I agree that the latter use case is more common in GCC, but I don't
> see it as a good thing. GCC was written in C and most code still
> uses now outdated C practices such as declaring variables at the top
> of a (often long) function, and usually
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758
--- Comment #20 from paul.richard.thomas at gmail dot com ---
Hi Dmitry,
I will persist with 81758 until I have a satisfactory testcase and
then I promise that I will move to 80850.
Cheers
Paul
On 26 October 2017 at 15:20, liakhdi at ornl
Martin Sebor writes:
>> /* The tree and const_tree overload templates. */
>> namespace wi
>> {
>> + class unextended_tree
>> + {
>> + private:
>> +const_tree m_t;
>> +
>> + public:
>> +unextended_tree () {}
>
>
On Wed, 25 Oct 2017, Jim Wilson wrote:
> The current documentation doesn't explain what the option is for, or
> how one might use it. The attached patch expands the documentation a
> bit to try to explain this.
> OK?
Thanks you for fleshing this out, Jim!
This looks fine to me (modula Sandra's
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82736
--- Comment #4 from Federico Kircheis ---
Thank you very much for your feedback.
With "-static" or "-static-libstdc++" i got the expected (at least for me)
result.
I guess that I'll need to register to https://sourceware.org/bugzilla/ to ask
On Wed, Oct 25, 2017 at 07:11:07PM -0500, Segher Boessenkool wrote:
> Hi Mike,
>
> On Sat, Oct 21, 2017 at 09:09:58AM -0400, Michael Meissner wrote:
> > As Segher and I were discussing off-line, I have some problems with the
> > current
> > -mabi={ieee,ibm}longdouble switches as we start to
This one.
https://gcc.gnu.org/ml/gcc-patches/2017-10/msg00537.html
There was discussion about documenting this, but the actual configure
change hasn't been reviewed yet.
-Sandra
GCC's default optimization level is -O0. Unfortunately unlike other compilers,
GCC generates extremely inefficient code with -O0. It is almost unusable for
low-level debugging or manual inspection of generated code. So a -O option is
always required for compilation. -Og not only allows for
On 26/10/17 18:55 +0200, Daniel Krügler wrote:
2017-10-26 7:51 GMT+02:00 François Dumont :
Hi
We once talk about rename the __cxx1998 namespace into something less
C++98 biased. Here is the patch to do so.
Ok with the new name ?
IMO the name should somehow
On 10/25/2017 06:26 PM, Jim Wilson wrote:
Index: gcc/doc/invoke.texi
===
--- gcc/doc/invoke.texi (revision 254023)
+++ gcc/doc/invoke.texi (working copy)
@@ -6981,7 +6981,12 @@ link processing time. Merging is enabled by defau
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82704
--- Comment #2 from Keno Fischer ---
Well, the script has a separate code path for Darwin anyway, since Darwin's
sha512sum is spelled `shasum -a 512`, but `shasum` also supports `-c` (as well
as `--check`).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78809
Paolo Carlini changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82736
--- Comment #3 from Jonathan Wakely ---
This might also be due to how glibc defines the clock_gettime symbol (as a weak
alias for its internal __clock_gettime), in which case it would still belong in
https://sourceware.org/bugzilla/ but for
2017-10-26 7:51 GMT+02:00 François Dumont :
> Hi
>
> We once talk about rename the __cxx1998 namespace into something less
> C++98 biased. Here is the patch to do so.
>
> Ok with the new name ?
IMO the name should somehow still contain "cxx" somewhere, otherwise
this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82736
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
On 10/26/2017 03:24 AM, Richard Biener wrote:
> On Tue, Oct 24, 2017 at 8:44 PM, Jeff Law wrote:
>> This is similar to the introduction of the ssa_propagate_engine, but for
>> the substitution/replacements bits.
>>
>> In a couple places the pass specific virtual functions are
Hi,
I am looking into DSE transformation of some fortran codes. Given
below fortran declarations:
real*8 a(len) , b(len) , c(len) , d(len)
common /area/ a, b, c, d
real*8 src1(len), temp1(len), temp2(len), src2(len)
equivalence(src1, a), (src2, b),
The documentation for the "-mabi" argument on RISC-V was incorrect. We
chose to treat this as a documentation bug rather than a code bug, and
to make the documentation match what GCC currently does. In the
process, I also improved the documentation a bit.
Thanks to Alex Bradbury for finding the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82735
--- Comment #1 from Marcin Ślusarz ---
Heh, there are really stupid bugs in both files. Thankfully they don't change
the outcome.
Updated code:
$ cat main.c
#include
#include
void test(char *dest);
int main()
{
char buf[64];
/* The tree and const_tree overload templates. */
namespace wi
{
+ class unextended_tree
+ {
+ private:
+const_tree m_t;
+
+ public:
+unextended_tree () {}
Defining no-op ctors is quite dangerous and error-prone. I suggest
to instead default initialize the member(s):
1 - 100 of 270 matches
Mail list logo