https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96829
Bug ID: 96829
Summary: implement -fsanitize=unsigned-integer-overflow
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96810
--- Comment #2 from Wei Wentao ---
> --- Comment #1 from Jakub Jelinek ---
> >The standard says this is unspecified behavior, but the unspecified behavior
> >happens at runtime, so if the compiler could detect it at compile time, it
> >would
> If x_2 is a default def then the IL isn't correct in the first place. I doubt
> it is that way, btw. - we have verifiers that would blow up if it would.
Richard,
I'm just sharing this so you can tell me whether or not I'm going
crazy. ;-)
This little function is finding that arr_2 = PHI
is
On Thu, Aug 27, 2020 at 03:47:19PM -0500, will schmidt wrote:
> > (Fm): New mode attribute for floating point scalars.
>
> Mixed feels on mixed case, but I defer. :-)
It is similar to other mode attributes (Ff, Fv) used for setting constraints
based on the mode.
--
Michael Meissner, IBM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96828
Bug ID: 96828
Summary: Wrong code generated with -fstack-protector and
-msingle-pic-base
Product: gcc
Version: 10.1.1
Status: UNCONFIRMED
Severity: normal
Hi Iain
Iain Sandoe wrote:
>Richard Sandiford wrote:
>> "Qian, Jianhua" writes:
>>> Hi Richard
>>>
>>> I found that some instructions are using '#' before immediate value，
>>> and others are not. For example
>>> (define_insn "insv_imm"
>>> [(set (zero_extract:GPI (match_operand:GPI 0
nux-gnu
Configured with: /home/sqwishy/src/gcc/configure --enable-languages=c
--disable-multilib
gcc version 11.0.0 20200827 (experimental) (GCC)
This is the command and output of compiling the attached file (min.i) with the
version of gcc I built from a recent checkout.
> ./usr/local/bin/g
#pragma region is a feature introduced by Microsoft in order to allow
manual grouping and folding of code within Visual Studio. It is
entirely ignored by the compiler. Clang has supported this feature
since 2012 when in MSVC compatibility mode, and enabled it across the
board 3 months ago.
As
On Thu, Aug 27, 2020 at 03:17:45PM -0500, Segher Boessenkool wrote:
> On Thu, Aug 27, 2020 at 01:51:25PM -0500, Bill Schmidt wrote:
> It not the copy that is unnecessary: the preventing it *here*, manually,
> is what is unnecessary.
Blame me for the original !rtx_equal_p in rs6000_call_aix that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96728
--- Comment #4 from José Rui Faustino de Sousa ---
Hi Paul,
Sorry for the confusion. I did not knew I could (should) have assigned it to
myself.
Sorry for the wasted time.
Thank you very much.
Best regards,
José Rui
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96791
acsawdey at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |acsawdey at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96824
--- Comment #3 from gcc_bugzilla at gabryjelski dot com ---
Ok, thanks for taking a look. Glad to hear it's just old version on
godbolt.org.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798
--- Comment #2 from Dominique d'Humieres ---
> What does the declaration of memset look like in your headers?
> (including attributes)
void*memset(void *__b, int __c, size_t __len);
With --enable-valgrind-annotations the change to the member function
signature in this patch triggers compilation errors during bootstrap:
/src/gcc/trunk/gcc/ggc-common.c: In function ‘void gt_pch_save(FILE*)’:
/src/gcc/trunk/gcc/ggc-common.c:509:33: error: no matching function for
call to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96791
--- Comment #4 from Bill Schmidt ---
Not the partially dead store code after all -- just a coincidence!
This libgo patch by Maciej W. Rozycki removes a middle dot from the
gotest shell script. There was a U+00B7 middle dot character, placed
after "mips64p32le" in the target lists, which is now changed to a
space. The U+00B7 character may not be considered whitespace by
Bourne shell and any
Hi,
this patch adds two static methods to ipa_call_context which construct
and return the object in the two scenarios where we use them (what if
an edge was inlined, what if a node wascloned) which saves callers a
bit work and are more intuitive.
The next step is to make
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798
--- Comment #1 from David Malcolm ---
Sorry about the failures.
I attempted to reproduce this via building a cross-compiler with
build==host==x86_64-pc-linux-gnu and --target=x86_64-apple-darwin19.6; I think
this comes down to the tests in
Snapshot gcc-8-20200827 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/8-20200827/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 8 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
I may be missing an obvious workaround, but it seems we currently emit
a #line directive when including lines from machine description files
in C files, but never emit a second directive when switching back to
the generated C file. This makes stepping through the backend in gdb
somewhat painful,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96826
Martin Sebor changed:
What|Removed |Added
Blocks||83819
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96826
Bug ID: 96826
Summary: missing warning appending to the result of strdup
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
Hi, Honza.
Again, thank you for your detailed review!
On 08/27, Jan Hubicka wrote:
> > When using the LTO infrastructure to compile files in parallel, we
> > can't simply use any of the LTO partitioner, once extra dependency
> > analysis is required to ensure that some nodes are correctly
> >
This implements the changes from P0548 "common_type and duration". That
was a change for C++17, but as it corrects some issues introduced by DRs
I'm also treating it as a DR and changing it for all modes from C++11
up.
The main change is that duration::period no longer denotes P, but
rather
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89102
--- Comment #9 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:82030d51017323c5706d58d8c8626324ece007e4
commit r11-2913-g82030d51017323c5706d58d8c8626324ece007e4
Author: Jonathan Wakely
Date:
Hi,
this large patch is a semi-mechanical change which aims to replace
uses of separate vectors about known scalar values (usually called
known_vals or known_csts), known aggregate values (known_aggs), known
virtual call contexts (known_contexts) and known value
ranges (known_value_ranges) with
On Thu, 27 Aug 2020, Martin Sebor via Gcc-patches wrote:
> The attached change has match_builtin_function_types() fail
> for erroneous argument types to prevent an ICE due to assuming
> they are necessarily valid.
OK.
--
Joseph S. Myers
jos...@codesourcery.com
On Wed, 2020-08-26 at 22:46 -0400, Michael Meissner via Gcc-patches wrote:
> PowerPC: Add power10 xscmp{eq,gt,ge}qp support.
>
> This patch adds the conditional move support. In adding the conditional move
> support, the optimizers will be able to convert things like:
>
> a = (b > c) ? b
On Wed, 2020-08-26 at 22:45 -0400, Michael Meissner via Gcc-patches wrote:
> PowerPC: Add power10 xsmaxcqp/xsmincqp support.
>
> This patch adds support for the ISA 3.1 (power10) IEEE 128-bit "C" minimum and
> maximum functions. Because of the NaN differences, the built-in functions
> will
>
On Wed, 2020-08-26 at 22:44 -0400, Michael Meissner via Gcc-patches wrote:
> PowerPC: Rename functions for min, max, cmove.
>
> This patch renames the functions that generate the ISA 3.0 C minimum, C
> maximum, and conditional move instructions to use a better name than just
> using
> a _p9
On Wed, 2020-08-26 at 22:43 -0400, Michael Meissner via Gcc-patches wrote:
> PowerPC: Change cmove function return to bool.
>
> In doing the other work for adding ISA 3.1 128-bit minimum, maximum, and
> conditional move support, I noticed the two functions that process conditional
> moves return
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85487
Baruch Burstein changed:
What|Removed |Added
CC||bmburstein at gmail dot com
---
Excerpts from Jakub Jelinek's message of August 27, 2020 12:06 pm:
> On Fri, Jul 31, 2020 at 04:28:05PM -0400, Jason Merrill via Gcc-patches wrote:
>> On 7/31/20 6:06 AM, Jakub Jelinek wrote:
>> > On Fri, Jul 31, 2020 at 10:54:46AM +0100, Jonathan Wakely wrote:
>> > > > Does the standard require
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96818
--- Comment #7 from Jakub Jelinek ---
Judging from what other passes do with gimple switches and especially what the
tree-cfg.c switch verifier checks, the only requirement is that the index as
well as CASE_LOW/HIGH types are integral, all case
Hi!
On Thu, Aug 27, 2020 at 08:47:19PM +0800, Jojo R wrote:
> +insn-emit-split-c = $(foreach o, $(shell for i in
> {1..$(insn-generated-split-num)}; do echo $$i; done), insn-emit$(o).c)
If you use a variable for the result of that "seq", this will be more
readable / maintainable / etc.
(Should
On Thu, Aug 27, 2020 at 01:51:25PM -0500, Bill Schmidt wrote:
> >>+ /* For ELFv2, r12 and CTR need to hold the function address
> >>+ for an indirect call. */
> >>+ if (GET_CODE (func_desc) != SYMBOL_REF && DEFAULT_ABI == ABI_ELFv2)
> >>+{
> >>+ r12 = gen_rtx_REG (Pmode, 12);
> >>+
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96825
Bug ID: 96825
Summary: Commit r11-2645 degrades CPU2017 548.exchange2_r by
35%
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Due to revisions to hppa_rtx_costs by Roger Sayle, we now have shift add
instructions in
the shadd-2.c test. Committed to trunk and gcc-10 branch.
Dave
Fix shadd-2.c scan assembler count.
2020-08-27 John David Anglin
gcc/testsuite/
* gcc.target/hppa/shadd-2.c: Adjust times to 4.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96813
Aldy Hernandez changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96818
Aldy Hernandez changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85830
--- Comment #4 from Carl Love ---
Just remove
#define vec_popcntb __builtin_vec_vpopcntub
#define vec_popcnth __builtin_vec_vpopcntuh
#define vec_popcntw __builtin_vec_vpopcntuw
#define vec_popcntd __builtin_vec_vpopcntud
from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96791
--- Comment #3 from acsawdey at gcc dot gnu.org ---
This also requires -mbig which may be implicit in the original poster's build.
But I see it failing as well.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96805
Patrick Palka changed:
What|Removed |Added
CC||dcb314 at hotmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96732
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85830
--- Comment #3 from Steven Munroe ---
(In reply to Carl Love from comment #2)
> Hit the save button a little too fast missed putting in everything I
> intended to put in. Lets try to get it all in.
>
> > In altivec.h they are defined as:
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96818
Aldy Hernandez changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #5 from Aldy
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96811
--- Comment #4 from Steve Kargl ---
On Thu, Aug 27, 2020 at 04:57:14PM +, burnus at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96811
>
> --- Comment #3 from Tobias Burnus ---
> (In reply to kargl from comment #2)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96791
Bill Schmidt changed:
What|Removed |Added
CC||luoxhu at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96790
Johel Ernesto Guerrero Peña changed:
What|Removed |Added
Keywords|rejects-valid |wrong-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65816
Johel Ernesto Guerrero Peña changed:
What|Removed |Added
CC||johelegp at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96818
Aldy Hernandez changed:
What|Removed |Added
CC||dcb314 at hotmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96823
Aldy Hernandez changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87798
--- Comment #2 from Aldy Hernandez ---
And a C version:
int a, b, c;
void d() {
unsigned short e;
while (b)
;
e = (e + 5) / 0;
switch (e)
case 0:
case 3:
c = a;
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96818
Aldy Hernandez changed:
What|Removed |Added
CC||jason at redhat dot com,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96824
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87798
Aldy Hernandez changed:
What|Removed |Added
CC||aldyh at gcc dot gnu.org
Ever
Hi Roger,
On 2020-08-27 12:42 p.m., Roger Sayle wrote:
> I was wondering whether you could please "put this in the queue", and
> reconfirm that PR middle-end/87256 remains resolved?
>
>
> 2020-08-27 Roger Sayle
>
> gcc/ChangeLog
> * config/pa/pa.c (hppa_rtx_costs) [ASHIFT, ASHIFTRT,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92942
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
Hi!
On 8/27/20 1:41 PM, Segher Boessenkool wrote:
Hi!
On Thu, Aug 27, 2020 at 08:21:34AM -0500, Bill Schmidt wrote:
+ /* For ELFv2, r12 and CTR need to hold the function address
+ for an indirect call. */
+ if (GET_CODE (func_desc) != SYMBOL_REF && DEFAULT_ABI == ABI_ELFv2)
+{
+
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96791
David Edelsohn changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96824
David Malcolm changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
Hi!
On Thu, Aug 27, 2020 at 08:21:34AM -0500, Bill Schmidt wrote:
> + /* For ELFv2, r12 and CTR need to hold the function address
> + for an indirect call. */
> + if (GET_CODE (func_desc) != SYMBOL_REF && DEFAULT_ABI == ABI_ELFv2)
> +{
> + r12 = gen_rtx_REG (Pmode, 12);
> +
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96824
Bug ID: 96824
Summary: segfault during IPA pass: analyzer (very simple code)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
On Thu, Aug 27, 2020 at 08:43:40AM -0700, Carl Love wrote:
> 2020-08-26 Carl Love
> * config/rs6000/rs6000-builtin.def: (BU_P10V_VSX_1) New builtin macro
> expansion.
> (XVCVBF16SPN, XVCVSPBF16): Replace macro expansion BU_VSX_1 with
> BU_P10V_VSX_1.
> *
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96822
Aldy Hernandez changed:
What|Removed |Added
Depends on||96818
--- Comment #1 from Aldy
Hi, Honza.
Thank you for your detailed review!
On 08/27, Jan Hubicka wrote:
> > diff --git a/gcc/cgraph.c b/gcc/cgraph.c
> > index c0b45795059..22405098dc5 100644
> > --- a/gcc/cgraph.c
> > +++ b/gcc/cgraph.c
> > @@ -226,6 +226,22 @@ cgraph_node::delete_function_version_by_decl (tree
> > decl)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96818
Aldy Hernandez changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |aldyh at gcc dot gnu.org
---
:
c = a;
}
broke in this way:
/home/dcb/gcc/results.20200826/bin/gcc
/home/dcb/gcc/results.20200827/bin/gcc
during GIMPLE pass: vrp
resample_f.c: In function ‘rs_vib_loop’:
resample_f.c:3230:20: internal compiler error: in decompose, at wide-int.h:984
0xfc1e55 irange::irange_intersect(irange const
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85830
--- Comment #2 from Carl Love ---
Hit the save button a little too fast missed putting in everything I intended
to put in. Lets try to get it all in.
(In reply to Carl Love from comment #1)
> The Power 64-Bi ELF V2 ABI specification revision
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96813
Aldy Hernandez changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |aldyh at gcc dot gnu.org
---
On Thu, 2020-08-27 at 17:42 +0100, Roger Sayle wrote:
> Hi Dave (and Jeff),
> For your consideration, here's a patch that should fix the recent regression
> of gcc.dg/tree-ssa/slrt-13.c on hppa targets.
>
> This patch provides more accurate rtx_costs estimates for shifts by
> integer constants
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85830
Carl Love changed:
What|Removed |Added
CC||cel at us dot ibm.com
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96822
Bug ID: 96822
Summary: [11 regression] Starting with r11-2833 ICE in
decompose, at wide-int.h:984
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity:
On 8/14/20 11:04 AM, Jeff Chapman wrote:
Hello!
Attached is a patch that fixes an ICE on the devel/c++-modules branch caused
by a slot invalidation edge case in push_namespace.
I just fell over this myself, reducing a testcase. your fix wasn;t
quite right -- we were creating an empty slot
On August 27, 2020 7:45:15 PM GMT+02:00, Gary Oblock
wrote:
>Richard,
>
>>You need to call update_stmt () if you change SSA operands to
>>sth else.
>
>I'm having trouble parsing the "sth else" above. Could you
>please rephrase this if it's important to your point. I take
>what you mean is if you
Richard,
>You need to call update_stmt () if you change SSA operands to
>sth else.
I'm having trouble parsing the "sth else" above. Could you
please rephrase this if it's important to your point. I take
what you mean is if you change any SSA operand to any
statement then update that statement.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96596
Martin Sebor changed:
What|Removed |Added
Keywords||patch
Assignee|unassigned at
The attached change has match_builtin_function_types() fail
for erroneous argument types to prevent an ICE due to assuming
they are necessarily valid.
Martin
PR c/96596 - ICE in match_builtin_function_types on a declaration of a built-in with invalid array argument
gcc/c/ChangeLog:
PR c/96596
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96821
--- Comment #1 from Daniil Dudkin ---
Considering the code below the correct output would be (without the
indentation):
Called with constant value
Called with non-const value
But the actual output is:
Called with constant value
Called
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95882
markeggleston at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95882
--- Comment #5 from CVS Commits ---
The releases/gcc-9 branch has been updated by Mark Eggleston
:
https://gcc.gnu.org/g:042c58a4b8ba48fdf26c9003154e9d3b83d4c568
commit r9-8836-g042c58a4b8ba48fdf26c9003154e9d3b83d4c568
Author: Mark Eggleston
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96821
Bug ID: 96821
Summary: [concepts] Incorrect evaluation of concept with
ill-formed expression
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Hello,
Following on from the earlier patch to fix up the syntax for
add/sub/adds/subs and friends with a sign/zero-extended operand [0],
this patch removes the "mult" variants of these patterns which are
all redundant.
This patch removes the following patterns from the AArch64 backend:
On Thu, Aug 27, 2020 at 4:45 PM H.J. Lu wrote:
> > > > > > How about target("baseline-isas-only")? All CPUID functions are
> > > > > > inlined.
> > > > >
> > > > > No, I don't think this is a good idea. Now consider the situation that
> > > > > caller functions are compiled with e.g.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96811
--- Comment #3 from Tobias Burnus ---
(In reply to kargl from comment #2)
> For real x, gfortran does not generate a call to libgfortran function.
It does – as mentioned in my email reply but not only for 'int' integers:
integer(16) :: n
real
"Kewen.Lin" writes:
> Hi Richard,
>
>>> Yeah, the comments were confusing, its intent is to check which targets
>>> support partial vectors and which usage to be used.
>>>
>>> How about to update them like:
>>>
>>> "Return true if loops using partial vectors are supported and usage kind is
>>>
On 27/08/20 12:37 -0400, Patrick Palka wrote:
On Thu, 27 Aug 2020, Jonathan Wakely wrote:
On 27/08/20 11:29 -0400, Patrick Palka via Libstdc++ wrote:
> This fixes the months-based addition for year_month when the
> year_month's month component is zero.
>
> Successfully tested on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65146
--- Comment #24 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:04df5e7de2f3dd652a9cddc1c9adfbdf45947ae6
commit r11-2909-g04df5e7de2f3dd652a9cddc1c9adfbdf45947ae6
Author: Jakub Jelinek
Date:
Hi Dave (and Jeff),
For your consideration, here's a patch that should fix the recent regression
of gcc.dg/tree-ssa/slrt-13.c on hppa targets.
This patch provides more accurate rtx_costs estimates for shifts by
integer constants (which are cheaper than by a register amount).
Fine tuning these is
On Thu, 27 Aug 2020, Jonathan Wakely wrote:
> On 27/08/20 11:29 -0400, Patrick Palka via Libstdc++ wrote:
> > This fixes the months-based addition for year_month when the
> > year_month's month component is zero.
> >
> > Successfully tested on x86_64-pc-linux-gnu, on the 'date' library's
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96818
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96811
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=96787
Bill Schmidt changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83700
Bug 83700 depends on bug 79097, which changed state.
Bug 79097 Summary: coarray and pointer component
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79097
What|Removed |Added
On 25/08/20 15:47 -0400, Patrick Palka via Libstdc++ wrote:
My original patch that implemented the calendar type operations failed
to enforce a constraint on some of the addition/subtraction operator
overloads that take a 'months' argument:
Constraints: If the argument supplied by the caller
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79097
Andre Vehreschild changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96787
--- Comment #9 from CVS Commits ---
The master branch has been updated by William Schmidt :
https://gcc.gnu.org/g:abca87c57847cd04f5e05935ff9ae5121c1ecb1d
commit r11-2908-gabca87c57847cd04f5e05935ff9ae5121c1ecb1d
Author: Bill Schmidt
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95882
--- Comment #4 from CVS Commits ---
The releases/gcc-10 branch has been updated by Mark Eggleston
:
https://gcc.gnu.org/g:8323d09e82345a1ca39f6630cdd22ccf4ef38a84
commit r10-8679-g8323d09e82345a1ca39f6630cdd22ccf4ef38a84
Author: Mark Eggleston
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96819
--- Comment #11 from Jonathan Wakely ---
And bisecting with -std=c++20 instead of -std=c++20 confirms it was r11-2747.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96805
Jonathan Wakely changed:
What|Removed |Added
CC||gccbugbjorn at fahller dot se
---
1 - 100 of 247 matches
Mail list logo
