https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93418
Jakub Jelinek changed:
What|Removed |Added
Summary|[9/10 Regression] GCC |[9 Regression] GCC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93418
--- Comment #9 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:bff948aa337807260344c83ac9079d6386410094
commit r10-6273-gbff948aa337807260344c83ac9079d6386410094
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93454
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93454
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:3c076c9642fd8877def0a0597ec7e4adfb5aa3b3
commit r10-6272-g3c076c9642fd8877def0a0597ec7e4adfb5aa3b3
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93399
--- Comment #5 from Alexandre Oliva ---
I suppose it would make sense for str_pattern_slim to quote line breaks
and other active characters when printing out string literals. And
perhaps to eliminate one more use of str_pattern_slim while at
On Mon, Jan 27, 2020 at 09:09:37PM -0500, David Malcolm wrote:
> > Please see calls.c (special_function_p), you should treat certainly
> > also sigsetjmp as a setjmp call, and similarly to special_function_p,
> > skip over _ or __ prefixes before the setjmp or sigsetjmp name.
> > Similarly for
On Tue, 28 Jan 2020, Uecker, Martin wrote:
> > (*) this also shows the level of "obfuscation" needed to fool compilers
> > to lose provenance knowledge is hard to predict.
>
> Well, this is exactly the problem we want to address by defining
> a clear way to do this. Casting to an integer would
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93272
--- Comment #5 from Andreas Krebbel ---
(In reply to Vladimir Makarov from comment #4)
> (In reply to Andreas Krebbel from comment #3)
> > Created attachment 47714 [details]
> > IRA EH fix - only when added at start of BB
> >
> > A probably
On Mon, Jan 27, 2020 at 3:13 PM H.J. Lu wrote:
>
> There are
>
> static void
> parse_mtune_ctrl_str (bool dump)
> {
> if (!ix86_tune_ctrl_string)
> return;
>
> parse_mtune_ctrl_str is only called from set_ix86_tune_features, which
> is only called from ix86_function_specific_restore and
>
On Mon, Jan 27, 2020 at 11:17 PM H.J. Lu wrote:
>
> On Mon, Jan 27, 2020 at 12:26 PM Uros Bizjak wrote:
> >
> > On Mon, Jan 27, 2020 at 7:23 PM H.J. Lu wrote:
> > >
> > > movaps/movups is one byte shorter than movdaq/movdqu. But it isn't the
> > > case for AVX nor AVX512. We should disable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92169
Dmitry G. Dyachenko changed:
What|Removed |Added
CC||dimhen at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92137
--- Comment #7 from Eric Gallager ---
(In reply to Ariel Torti from comment #6)
> (In reply to Eric Gallager from comment #5)
> > (In reply to Jakub Jelinek from comment #3)
> > > Those are intrinsics and most of them are documented in the Intel
Hi,
This patch fixes GDC on s390x-linux-musl targets. It was specifically
tested under Alpine Linux (see
https://gitlab.alpinelinux.org/alpine/aports/commit/c123e0f14ab73976a36c651d47d134f249413f29
).
The patch fixes two issues: First, Musl always provide
`__tls_get_addr`, so we can always use it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93476
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93476
Bug ID: 93476
Summary: int bit fields waste space
Product: gcc
Version: 7.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93475
Bug ID: 93475
Summary: With 100k+ mangled names, appears to incorrectly
mangle about 15% causing demangle failure
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
On Wed, 2020-01-22 at 20:40 +0100, Jakub Jelinek wrote:
> On Wed, Jan 22, 2020 at 02:35:13PM -0500, David Malcolm wrote:
> > PR analyzer/93316 reports various testsuite failures where I
> > accidentally relied on properties of x86_64-pc-linux-gnu.
> >
> > The following patch fixes them on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82407
Bug 82407 depends on bug 93451, which changed state.
Bug 93451 Summary: ICE: qsort checking failed (error: qsort comparator
non-negative on sorted output: 0)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93451
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93451
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93452
Andrew Pinski changed:
What|Removed |Added
Keywords||diagnostic, rejects-valid
PR analyzer/93451 reports an ICE when canonicalizing the constants
in a region_model, with a failed qsort_chk when attempting to sort
the constants within the region_model.
The svalues in the model were:
sv0: {poisoned: uninit}
sv1: {type: ‘double’, ‘0.0’}
sv2: {type: ‘double’, ‘1.0e+0’}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93451
--- Comment #2 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:8c08c983015e675f555d57a30e15d918abef2b93
commit r10-6271-g8c08c983015e675f555d57a30e15d918abef2b93
Author: David Malcolm
Date:
Hi Richard,
thank you for your response.
Am Montag, den 27.01.2020, 15:42 +0100 schrieb Richard Biener:
> On Fri, Jan 24, 2020 at 12:46 AM Uecker, Martin
> wrote:
> >
> > Am Donnerstag, den 23.01.2020, 14:18 +0100 schrieb Richard Biener:
> > > On Wed, Jan 22, 2020 at 12:40 PM Martin Sebor
On Mon, Jan 27, 2020 at 2:17 PM H.J. Lu wrote:
>
> On Mon, Jan 27, 2020 at 12:26 PM Uros Bizjak wrote:
> >
> > On Mon, Jan 27, 2020 at 7:23 PM H.J. Lu wrote:
> > >
> > > movaps/movups is one byte shorter than movdaq/movdqu. But it isn't the
> > > case for AVX nor AVX512. We should disable
borm/heads/sra-later_total-bfr-20200127 or look at
https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;a=shortlog;h=refs/users/jamborm/heads/sra-later_total-bfr-20200127
if you are interested), but this approach meant that each such
extended replacement which was written to (so all of them) could
potentia
Hi,
this patch fixes the second testcase in PR 92706 by performing total
scalarization only quite a bit later, when we already have access
trees constructed and even done propagation of accesses from RHSs of
assignment to LHSs.
The new code simultaneously traverses the existing access tree and
Hi,
the previous patch unfortunately does not fix the first testcase in PR
92706 and since I am afraid it might be the important one, I also
focused on that. The issue here is again total scalarization accesses
clashing with those representing accesses in the IL - on another
aggregate but here
Hi,
this patch has not changed since the last submission at all, in fact
it got approved but without the follow-up fix of the reverse flag, it
would introduce regression, so it should not be committed on its own.
Because the follow-up patches perform some non-trivial operations on
SRA patches, I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90688
Jeffrey A. Law changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92610
--- Comment #5 from Jeffrey A. Law ---
*** Bug 90688 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93474
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91075
--- Comment #1 from joseph at codesourcery dot com ---
This would definitely be invalid C (the prior declaration visible in the
inner scope has no linkage, so the inner declaration has external linkage
and "If, within a translation unit, the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93474
Bug ID: 93474
Summary: no warning for nonstandard bit field
Product: gcc
Version: 7.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
On Tue, 2020-01-28 at 00:41 +0100, Jakub Jelinek wrote:
> Hi!
>
> The following testcase is miscompiled, because the variable shift left
> operand, { -1, -1, -1, -1 } is represented as a VECTOR_CST with
> VECTOR_CST_NPATTERNS 1 and VECTOR_CST_NELTS_PER_PATTERN 1, so when
> we call
On Tue, 2020-01-28 at 00:33 +0100, Jakub Jelinek wrote:
> Hi!
>
> libgcrypt FAILs to build on aarch64-linux with
> *** stack smashing detected ***: terminated
> when gcc is compiled with -D_FORTIFY_SOURCE=2. The problem is if
> fold_array_ctor_reference is called with size equal to or very close
On Mon, 2020-01-27 at 22:32 +, Andrew Burgess wrote:
> I know that the tree's currently closed to non-bugfix changes, but I
> was hoping this might be accpeted anyway so it can be backported to
> binutils-gdb.
>
> ---
>
> Makes some parameters const in libiberty's hashtab library.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93455
Andrew Pinski changed:
What|Removed |Added
Keywords||missed-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93380
--- Comment #3 from Andrew Pinski ---
(In reply to Robert Dumitru from comment #2)
> Hi Andrew,
>
> Thank you for your pointing out that. I will report the issue to ARM as well.
> However, regarding 1 and 2:
>
> 1. I understand this looks
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86793
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
read model: posix
Supported LTO compression algorithms: zlib
gcc version 10.0.1 20200127 (experimental) (GCC)
$ gfortran -c 1057.F90 -o test.o -ffree-line-length-none
f951: internal compiler error: Segmentation fault
0xe1021f crash_signal
../../gcc-git/gcc/toplev.c:328
0x7f
Hi!
The following testcase is miscompiled, because the variable shift left
operand, { -1, -1, -1, -1 } is represented as a VECTOR_CST with
VECTOR_CST_NPATTERNS 1 and VECTOR_CST_NELTS_PER_PATTERN 1, so when
we call builder.new_unary_operation, builder.encoded_nelts () will be just 1
and thus we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61926
--- Comment #4 from Andrew Pinski ---
(In reply to Martin Liška from comment #3)
> Can the bug be marked as resolved?
No, the testcases are just xfailed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91543
Jeffrey A. Law changed:
What|Removed |Added
CC||law at redhat dot com
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91474
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80306
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |8.0
--- Comment #3 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80306
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63882
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
Hi!
libgcrypt FAILs to build on aarch64-linux with
*** stack smashing detected ***: terminated
when gcc is compiled with -D_FORTIFY_SOURCE=2. The problem is if
fold_array_ctor_reference is called with size equal to or very close to
MAX_BITSIZE_MODE_ANY_MODE bits and non-zero inner_offset.
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92550
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92588
Jeffrey A. Law changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86793
--- Comment #1 from Andrew Pinski ---
So I can fix this for the Marvell/Cavium produced cores; Spectre workaround is
not needed though. Someone inside WaveComputing/MIPS would have to implement
this for those ones.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86290
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80656
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28126
--- Comment #13 from Andrew Pinski ---
> For now it is always emulated by kernel
Not on MIPS64r3/MIPS32r3 and above cores. Octeon2/3 implements this register.
There might be other cores which implement this register too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93473
--- Comment #2 from Andrew Benson ---
Problem occurs in set_syms_host_assoc() where the "parent1" and "parent2"
variables have a maximum length of GFC_MAX_SYMBOL_LEN+1. This is insufficient
when the parent names are a module+submodule name
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93473
--- Comment #1 from Andrew Benson ---
Created attachment 47722
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47722=edit
Proposed patch
Galacticus/Tools_Devel --enable-languages=c,c++,fortran
--disable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 10.0.1 20200127 (experimental) (GCC)
$ gfortran -c 1057.F90 -o test.o -ffree-line-length-none
f951: internal compiler error: Segmentation faul
Hi!
On Wed, Jan 22, 2020 at 07:11:27AM +0100, Hans-Peter Nilsson wrote:
> I intend to put back as many as I find use for, of those
> anonymous patterns in a controlled manner, with self-contained
> test-cases proving their usability, rather than symmetry with
> other instructions and similar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90731
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
I know that the tree's currently closed to non-bugfix changes, but I
was hoping this might be accpeted anyway so it can be backported to
binutils-gdb.
---
Makes some parameters const in libiberty's hashtab library.
include/ChangeLog:
* hashtab.h (htab_remove_elt): Make a parameter
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93437
--- Comment #2 from Andrew Pinski ---
(In reply to Rafael Avila de Espindola from comment #1)
> The warning is no longer issued after
> 6889a3acfeed47265886676c6d43b04ef799fb82.
g:6889a3acfeed47265886676c6d43b04ef799fb82
>
> Martin, is this a
On Mon, Jan 27, 2020 at 12:26 PM Uros Bizjak wrote:
>
> On Mon, Jan 27, 2020 at 7:23 PM H.J. Lu wrote:
> >
> > movaps/movups is one byte shorter than movdaq/movdqu. But it isn't the
> > case for AVX nor AVX512. We should disable TARGET_SSE_TYPELESS_STORES
> > for TARGET_AVX.
> >
> > gcc/
> >
>
On 1/24/20, Richard Earnshaw (lists) wrote:
> On 24/01/2020 10:27, Jonathan Wakely wrote:
>> On Fri, 24 Jan 2020 at 03:39, Nicholas Krause
>> wrote:
>>> Sorry for the second message Allan but make -j does not scale well
>>> beyond 4 or
>>> 8 threads and that's considering a 4 core or 8 machine.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93437
Rafael Avila de Espindola changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
* Jeff Law [2020-01-22 13:52:27 -0700]:
> On Wed, 2020-01-22 at 15:39 +, Andrew Burgess wrote:
> > The motivation behind this change is to make it easier for a user to
> > link against static libraries on a target where dynamic libraries are
> > the default library type (for example
On Mon, 2020-01-27 at 18:23 +, Joseph Myers wrote:
> mips_declare_object_name is missing the support for declaring symbols
> as gnu_unique_object that is present in the generic
> ASM_DECLARE_OBJECT_NAME in elfos.h. I'm not aware of any
> MIPS-specific reason for that support to be absent;
>
Hi!
On Tue, Jan 21, 2020 at 02:10:21PM +, Wilco Dijkstra wrote:
> While code hoisting generally improves codesize, it can affect performance
> negatively. Benchmarking shows it doesn't help SPEC and negatively affects
> embedded benchmarks. Since the impact is relatively small with -O2 and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93472
Bug ID: 93472
Summary: Document extended forms of constant expression
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
On Thu, 2019-12-12 at 15:44 -0500, Jason Merrill wrote:
> Here are the dumps from ssa-dom-thread-7.c made to compile as C++; cx-current
> is the dumps with current trunk; cx-old is changed to use the old goto-based
> lowering like C.
Sorry this has taken so long to get back to.
For
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93461
--- Comment #2 from Andrew Benson ---
The problem occurs because GFC_MAX_MANGLED_SYMBOL_LEN is set to
GFC_MAX_SYMBOL_LEN*2+4, which is sufficient for a module name plus function
name
(plus the additional "_"'s that get prepended), but
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93461
--- Comment #1 from Andrew Benson ---
Created attachment 47721
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47721=edit
Patch for PR93461
I created PR93461 for this issue: The following code causes a bogus "symbol is
already defined" error (using git commit
73380abd6b2783215c7950a2ade5e3f4b271e2bc):
module aModuleWithAnAllowedName
interface
module subroutine aShortName()
end subroutine aShortName
end interface
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93470
--- Comment #4 from frankhb1989 at gmail dot com ---
(In reply to Jonathan Wakely from comment #3)
> (In reply to frankhb1989 from comment #2)
> > Sorry, I missed to mention it only failed with `clang++ -std=c++2a`
>
> If you're going to claim
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93470
Jonathan Wakely changed:
What|Removed |Added
Status|WAITING |ASSIGNED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92463
Ian Lance Taylor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89627
Jim Wilson changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92463
--- Comment #8 from CVS Commits ---
The master branch has been updated by Ian Lance Taylor :
https://gcc.gnu.org/g:2f195832a12ff4fb54d723f32019d4175db1b5da
commit r10-6267-g2f195832a12ff4fb54d723f32019d4175db1b5da
Author: Ian Lance Taylor
This patch to the Go frontend adds cleanups now that MPFR 3.1.0 is
required. For MPFR functions, change from GMP_RND* to MPFR_RND*.
Also change mp_exp_t to mpfr_expt_t. This fixes GCC PR 92463.
Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu (with MPFR
4.0.2). Committed to mainline.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93459
--- Comment #2 from Marc Glisse ---
For __builtin_ia32_vec_ext_v4si, shouldn't we lower it to an array access in
gimple, when the second argument is constant? I assume we don't want to do it
directly in smmintrin.h for diagnostic purposes.
On Mon, Jan 27, 2020 at 7:23 PM H.J. Lu wrote:
>
> movaps/movups is one byte shorter than movdaq/movdqu. But it isn't the
> case for AVX nor AVX512. We should disable TARGET_SSE_TYPELESS_STORES
> for TARGET_AVX.
>
> gcc/
>
> PR target/91461
> * config/i386/i386.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93470
--- Comment #2 from frankhb1989 at gmail dot com ---
Case:
#include
void foo() {}
int main()
{
std::ref(foo)();
}
Sorry, I missed to mention it only failed with `clang++ -std=c++2a` (using
Clang++ 9.0.1). G++ with `-std=c++2a` still
On Mon, 27 Jan 2020, Ulrich Weigand wrote:
> I see. I guess that makes me wonder what -fno-fast-math *ever* does
> (except canceling a -ffast-math earlier on the command line). Looking
> at the current code, -fno-fast-math (just like -ffast-math) only ever
> sets flags whose default is not
Hi,
Did you had a chance to review my previous mail which I sent across?
If you are interested please revert me with your target requirement, so that
I can get back to you with more information on the counts and pricing.
Thank you and looking forward for your response.
Regards,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93471
Bug ID: 93471
Summary: GCC-9.2.0 libgomp configuration passes bogus mingw32
library search paths
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71625
--- Comment #25 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:8f25c39c454d7d3d323edf014a653649946352bd
commit r10-6266-g8f25c39c454d7d3d323edf014a653649946352bd
Author: Jason Merrill
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90966
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:8f25c39c454d7d3d323edf014a653649946352bd
commit r10-6266-g8f25c39c454d7d3d323edf014a653649946352bd
Author: Jason Merrill
Date:
Since Martin Sebor's patch for PR 71625 to change braced array initializers
to STRING_CST in some cases, we need to be ready for STRING_CST with types
that are changed by tsubst. fold_convert doesn't know how to deal with
STRING_CST, which is reasonable; we really shouldn't expect it to here. So
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93470
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93469
--- Comment #2 from Jonathan Wakely ---
This is a bug in your libc headers (and I'm guessing you're on OS X). The
aligned_alloc function should be declared for C++17 and later, irrespective of
the _XOPEN_SOURCE value.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93194
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93469
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
On Mon, 2019-12-16 at 11:18 +, Bader, Lucas wrote:
> Hello,
>
> within a compile cluster, only the preprocessed output of GCC is transferred
> to remote nodes for compilation.
> When GCC produces advanced diagnostics (with -fdiagnostics-show-caret), e.g.
> prints out the affected source
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93418
--- Comment #8 from Devin Hussey ---
Seems to work.
~ $ ~/gcc-test/bin/x86_64-pc-cygwin-gcc.exe -mavx2 -O3 _mm_sllv_bug.c
~ $ ./a.exe
Without optimizations (correct result): 8000 fff8
With optimizations (incorrect
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93470
Bug ID: 93470
Summary: [C++2a] std::reference_wrapper to function type is
broken
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93443
--- Comment #1 from CVS Commits ---
The master branch has been updated by Iain D Sandoe :
https://gcc.gnu.org/g:1f2e84238c9f079747804026b6225ec8c1d0e4b7
commit r10-6265-g1f2e84238c9f079747804026b6225ec8c1d0e4b7
Author: Iain Sandoe
Date: Mon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93469
Bug ID: 93469
Summary: memory header fails to compile with _XOPEN_SOURCE
macro defined and -std=c++2a option specified
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93468
--- Comment #2 from Svante Signell ---
Created attachment 47720
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47720=edit
Add hurd to // +build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93468
--- Comment #1 from Svante Signell ---
Created attachment 47719
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47719=edit
Add hurd to // +build
On Mon, Jan 13, 2020 at 01:12:15PM -0500, Eric S. Raymond wrote:
> Jonathan Wakely :
> > Email the patches to gcc-patches@gcc.gnu.org, that's how things get
> > merged.
> >
> > We're not looking to change any workflows now.
>
> Roger that.
>
> Once the dust from the conversion has settled,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93468
Bug ID: 93468
Summary: New patches to build gcc-10 on GNU/Hurd
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: go
1 - 100 of 385 matches
Mail list logo
