https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82193
--- Comment #6 from Andrew Pinski ---
Just a quick note p1787
(https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p1787r6.html) moves
around the place where it says no diagnostic is required but the effect is the
same.
it is now in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83705
Jerry DeLisle changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102595
Jerry DeLisle changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
Attached patch fixes this problem by allowing the namespace pointer to
be set correctly regardless of error condition.
Regression tested on x86_64_linux_gnu.
OK for trunk and backports?
Regards,
Jerry
Author: Jerry DeLisle
Date: Sat Jan 28 20:00:34 2023 -0800
ICE in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103506
--- Comment #14 from Jerry DeLisle ---
This is interesting. Simply doing the following eliminates the ice.
diff --git a/gcc/fortran/parse.cc b/gcc/fortran/parse.cc
index 0fb19cc9f0f..a9e538cc2a1 100644
--- a/gcc/fortran/parse.cc
+++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108587
Andrew Pinski changed:
What|Removed |Added
Resolution|INVALID |DUPLICATE
--- Comment #2 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82193
Andrew Pinski changed:
What|Removed |Added
CC||mserdarsanli at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108587
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108587
Bug ID: 108587
Summary: `decltype(x) x;` in struct declaration causes "changes
meaning of" error
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity:
Hi GCC developers,
I am learning GCC. But the GCC code is hard to understand.
I'm reading the c compiler of GCC. It seems the understanding of
AST/GENERIC representation is very important.
Is there a tool can visualize the AST/GENERIC representation?
Do you have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103585
--- Comment #15 from Jan Hubicka ---
We get 47s runtime with -O2 -flto and 53s with -O2
-fno-inline-functions-called-once.
The call sequence is:
[local count: 109362591]:
_1656 = (unsigned long) _45;
_1655 = _1656 + ivtmp.1182_2540;
Ready to push to trunk.
---
htdocs/gcc-12/changes.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 30fa4d6e..49055ffe 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -754,7 +754,7 @@
The official name is AVX512-FP16.
Ready to push to trunk.
gcc/ChangeLog:
* config/i386/i386.opt: Change AVX512FP16 to AVX512-FP16.
* doc/invoke.texi: Ditto.
---
gcc/config/i386/i386.opt | 2 +-
gcc/doc/invoke.texi | 6 +++---
2 files changed, 4 insertions(+), 4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108511
--- Comment #6 from Jan Hubicka ---
The function is used to discard early summaries that will lead to external
calls. This saves some memory allocations.
At this stage we have identified prevailing symbols and they are first in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108565
--- Comment #5 from Jan Hubicka ---
Teaching modref that THIS parameter of all destructors is nonescape looks like
interesting idea (and easy to implement).
Memory stores are currently indeed handled as "anyting may happen". modref does
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108585
--- Comment #5 from Andrew Pinski ---
"" will start to use the rep at 64*8 ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108552
--- Comment #39 from Jan Hubicka ---
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108552
>
> --- Comment #35 from Vladimir Makarov ---
> (In reply to Jakub Jelinek from comment #34)
> > Seems right now DECL_NONALIASED is only used on these
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108585
Andrew Pinski changed:
What|Removed |Added
Summary|Using std::byte instead of |memset uses SSE stores but
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108585
Andrew Pinski changed:
What|Removed |Added
Keywords||missed-optimization
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108585
--- Comment #2 from Andrew Pinski ---
*** Bug 108586 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108586
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108585
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108586
Bug ID: 108586
Summary: Using std::array instead of a plain array results in
different (worse?) code in array zero initialization
Product: gcc
Version: unknown
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108585
Bug ID: 108585
Summary: Using std::byte instead of char results in different
(worse?) code in array zero initialization
Product: gcc
Version: unknown
Status:
gcc/ChangeLog:
* config/aarch64/aarch64-cores.def (AARCH64_CORE): Update
ampere1a to include SM4.
Signed-off-by: Philipp Tomsich
---
gcc/config/aarch64/aarch64-cores.def | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/config/aarch64/aarch64-cores.def
Snapshot gcc-12-20230128 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20230128/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108582
--- Comment #6 from Andrew Pinski ---
Patch submitted:
https://gcc.gnu.org/pipermail/gcc-patches/2023-January/610817.html
This patch adds a check in match_simplify_replacement to make sure the middlebb
does not have any phi-nodes as we don't currently move those.
This was just a thinko from before.
Ok? Bootstrapped and tested on x86_64-linux-gnu with no regressions?
PR tree-optimization/108582
Pushed.
Gerald
gcc/ChangeLog:
* doc/extend.texi (Named Address Spaces): Update link to the
AVR-Libc manual.
---
gcc/doc/extend.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 027a08a2f62..5a026c4b48c 100644
Pushed.
Gerald
libstdc++-v3/ChangeLog:
* doc/xml/manual/appendix_contributing.xml: Adjust link to
ISO C++ standard at ANSI.
Move link to www.open-std.org to https.
* doc/html/manual/appendix_contributing.html: Regenerate.
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108529
--- Comment #5 from CVS Commits ---
The releases/gcc-12 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:a8ef7eec0c323a8752ad5babde6e4add4f224898
commit r12-9080-ga8ef7eec0c323a8752ad5babde6e4add4f224898
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106209
--- Comment #6 from CVS Commits ---
The releases/gcc-12 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:6dc4f984dd14ffad34e0540f2030f553579adefd
commit r12-9079-g6dc4f984dd14ffad34e0540f2030f553579adefd
Author: Harald Anlauf
Pushed.
Gerald
---
htdocs/gcc-11/porting_to.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/gcc-11/porting_to.html b/htdocs/gcc-11/porting_to.html
index 802fb367..a7b634c1 100644
--- a/htdocs/gcc-11/porting_to.html
+++ b/htdocs/gcc-11/porting_to.html
@@ -49,7
This is a minor variation of what i shared a week ago.
Pushed now, and I'll be happy to make adjustments/further changes based on
feedback.
Gerald
Break long sentences, fixe grammar, simplify language.
---
htdocs/projects/gomp/index.html | 29 ++---
1 file changed,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108420
--- Comment #6 from CVS Commits ---
The releases/gcc-12 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:523ee9f5994961b27c61d46b27dbe064f68d0d76
commit r12-9077-g523ee9f5994961b27c61d46b27dbe064f68d0d76
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108421
--- Comment #5 from CVS Commits ---
The releases/gcc-12 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:0e4c239ebde0a926832e3bcaae707eabf81927ff
commit r12-9078-g0e4c239ebde0a926832e3bcaae707eabf81927ff
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108501
--- Comment #7 from CVS Commits ---
The releases/gcc-12 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:daa4c49a4773f274b7a784cedd7b0e0b3c59523b
commit r12-9076-gdaa4c49a4773f274b7a784cedd7b0e0b3c59523b
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108502
--- Comment #4 from CVS Commits ---
The releases/gcc-12 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:4c6475148ac5d53449948665d7d94cfee5b549ac
commit r12-9075-g4c6475148ac5d53449948665d7d94cfee5b549ac
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108529
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Summary|[10/11/12/13 Regression]|[10/11/12 Regression] ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108527
--- Comment #9 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:22afa4947584c701633a79fd8750c9ceeaa96711
commit r13-5479-g22afa4947584c701633a79fd8750c9ceeaa96711
Author: Harald Anlauf
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108453
--- Comment #4 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:aba9ff8f30d4245294ea2583de1dc28f1c7ccf7b
commit r13-5478-gaba9ff8f30d4245294ea2583de1dc28f1c7ccf7b
Author: Harald Anlauf
Date:
Pushed.
Gerald
"." refers to the current directory; we need ".." to move one level up.
---
htdocs/projects/cxx-status.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
index f6435eb2..cc8fe615 100644
---
On 1/28/23 9:07 AM, Harald Anlauf via Fortran wrote:
Dear all,
a USE associated symbol shall not appear in a COMMON block
(F2018:C8121) and needs to be diagnosed. The patch is
fairly obvious.
Regtested on x86_64-pc-linux-gnu. OK for mainline?
As the PR is marked as a 10/11/12/13 regression,
On Sat, Jan 28, 2023 at 06:07:50PM +0100, Harald Anlauf via Fortran wrote:
>
> a USE associated symbol shall not appear in a COMMON block
> (F2018:C8121) and needs to be diagnosed. The patch is
> fairly obvious.
>
> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>
> As the PR is marked as
On 1/24/23 1:48 PM, Harald Anlauf via Fortran wrote:
Dear all,
when checking expressions for array sections, we need to ensure
that these use only type INTEGER. However, it does not make sense
to generate an internal error when encountering wrong types,
but rather take the ordinary route of
Hi Joe.
Sorry for the delay (1 year and 4 months) in responding
to this. There's a long and sad story as to what caused
the delay, but we're here now.
First of all, Hercules is a very important target. Even
if gcc -m31 only allowed writing above 2 GiB on Hercules,
that would still be an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108582
Andrew Pinski changed:
What|Removed |Added
Keywords||wrong-code
Target Milestone|13.0
/suz-local/software/local/gcc-trunk
--enable-sanitizers --enable-languages=c,c++ --disable-werror
--disable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 13.0.1 20230128 (experimental) [master r12-4647-g3f861a5c8fd] (GCC)
[595] %
[595] % gcctk -O3 small.c; ./a.out
[5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107360
Martin Uecker changed:
What|Removed |Added
CC||muecker at gwdg dot de
--- Comment #3
Pushed.
Gerald
gcc/ChangeLog:
* doc/standards.texi (Standards): Update link to Objective-C book.
---
gcc/doc/standards.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/doc/standards.texi b/gcc/doc/standards.texi
index b54502add41..5ea724f5657 100644
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108582
--- Comment #4 from Andrew Pinski ---
This should fix the issue:
apinski@xeond:~/src/upstream-gcc/gcc/gcc$ git diff tree-ssa-phiopt.cc
diff --git a/gcc/tree-ssa-phiopt.cc b/gcc/tree-ssa-phiopt.cc
index c3a889dc593..a7ab6ce4ad9 100644
---
Patch OK?
gcc/testsuite/ChangeLog:
* gcc.dg/pr65658.c: fix LLP64 test.From bd2634e2795723f290dcf4bbb06e70fb6ca6af51 Mon Sep 17 00:00:00 2001
From: Jonathan Yong <10wa...@gmail.com>
Date: Sat, 28 Jan 2023 18:12:50 +
Subject: [PATCH] pr65658.c: fix excess warnings on LLP64 targets
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103770
--- Comment #7 from Martin Uecker ---
Regression tests:
https://gcc.gnu.org/g:ebf7dd754a95bf9680bc53331a6b70f0cf83c045
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108582
--- Comment #3 from Andrew Pinski ---
PHI g_9 reduced for COND_EXPR in block 7 to g_8.
statement un-sinked:
k_22 = k_11 | iftmp.5_13;
Removing basic block 8
;; basic block 8, loop depth 0
;; pred: 7
# iftmp.5_13 = PHI <2(7)>
;; succ:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108582
Andrew Pinski changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108582
Andrew Pinski changed:
What|Removed |Added
Version|unknown |13.0
Ever confirmed|0
"[13 Regression]" OpenMP Fortran patches:
[Patch] OpenMP/Fortran: Fix loop-iter var privatization with !$OMP LOOP
[PR108512]
https://gcc.gnu.org/pipermail/gcc-patches/2023-January/610531.html
[Patch][v2] OpenMP/Fortran: Partially fix non-rect loop nests [PR107424]
I'm not fully confident if it might break other platforms. So hopefully
someone can comment on the patch.
gcc/testsuite/ChangeLog:
* c-c++-common/Wsizeof-array-div1.c: fix excess warnings.
* gcc.dg/Warray-bounds-52.c: ditto
* gcc.dg/Wstringop-overflow-62.c: ditto
Early gentle ping.
Am 24.01.23 um 22:48 schrieb Harald Anlauf via Gcc-patches:
Dear all,
when checking expressions for array sections, we need to ensure
that these use only type INTEGER. However, it does not make sense
to generate an internal error when encountering wrong types,
but rather
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108453
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
Dear all,
a USE associated symbol shall not appear in a COMMON block
(F2018:C8121) and needs to be diagnosed. The patch is
fairly obvious.
Regtested on x86_64-pc-linux-gnu. OK for mainline?
As the PR is marked as a 10/11/12/13 regression,
I plan to backport as appropriate.
Thanks,
Harald
Le 28/01/2023 à 03:47, Jerry D a écrit :
It is not apparent to me that the testsuite/ChangeLog was updated. Maybe
there is a time delay on that?
Yes, it's done daily as part of the "daily bump" commit.
You can see it in the git log:
$ git log -- gcc/testsuite/ChangeLog
commit
On 1/19/23 09:26, Jonathan Yong wrote:
On 1/11/23 09:56, Jonathan Yong wrote:
Are the patches and changelogs OK?
Ping1.
Pushed to master branch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108192
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jonathan Yong :
https://gcc.gnu.org/g:6464409b0c7077e36858989b5dae302e2d26f45a
commit r13-5475-g6464409b0c7077e36858989b5dae302e2d26f45a
Author: Jonathan Yong
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108150
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jonathan Yong :
https://gcc.gnu.org/g:ff3d99c5e72126cf8d4c7611a63a82dfc476cdbe
commit r13-5474-gff3d99c5e72126cf8d4c7611a63a82dfc476cdbe
Author: Jonathan Yong
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108580
--- Comment #8 from postmaster at raasu dot org ---
I know enough C that you can't write code like:
int i = 0x;
This is not equal to:
int i = -1;
or
int i = (-1);
---
Largest literal you can assign to "int" is "0x7FFF". Any
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108552
--- Comment #38 from Tang, Feng ---
Created attachment 54368
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54368=edit
objdump of prep_compound_page() with patch in comment 35
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108552
--- Comment #37 from Tang, Feng ---
Created attachment 54367
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54367=edit
page_alloc.i with patch in comment 35
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108552
--- Comment #36 from Tang, Feng ---
(In reply to Vladimir Makarov from comment #35)
> (In reply to Jakub Jelinek from comment #34)
> > Seems right now DECL_NONALIASED is only used on these coverage vars and on
> > Fortran caf tokens, so perhaps
On Tue, 2023-01-17 17:25:08 +0100, Jose E. Marchesi via Gcc-patches
wrote:
> The stack protector is not supported in BPF. This patch disables
> -fstack-protector in bpf-* targets, along with the emission of a note
> indicating that the feature is not supported in this platform.
[...]
> diff
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108583
Bug ID: 108583
Summary: [13 Regression] wrong code with vector division by
uint16 at -O2
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: wrong-code
ported LTO compression algorithms: zlib
gcc version 13.0.1 20230128 (experimental) [master r12-4647-g3f861a5c8fd] (GCC)
[618] %
[618] % gcctk -O3 small.c; ./a.out
[619] %
[619] % gcctk -O3 -fno-tree-ccp -fno-tree-dce small.c
during GIMPLE pass: phiopt
small.c: In function ‘main’:
small.c:3:5: interna
Now we claim options for Modula-2 in m2/lang.opt we need to add those
used for warnings too.
This fixes:
FAIL: gm2/warnings/returntype/pass/Termbase.mod
FAIL: gm2/warnings/returntype/pass/goodreturn.mod
FAIL: gm2/warnings/returntype/pass/keypressedsimple.mod
all with -O0 -g -Werror=return-type
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108580
--- Comment #7 from Andrew Pinski ---
Wrong again.
In c, 1 is int, if you want unsigned int type use 1u.
This forum is not to learn C and it is obvious you don't know the basics of the
language.
Pushed.
Gerald
---
htdocs/bugs/index.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html
index 96a5d0f0..765d8c67 100644
--- a/htdocs/bugs/index.html
+++ b/htdocs/bugs/index.html
@@ -629,7 +629,7 @@ section of the GCC manual.
On Fri, 8 Oct 2021, Hongtao Liu wrote:
> > On Fri, 24 Sep 2021, Hongtao Liu via Gcc-patches wrote:
>>> + New ISA extension support for Intel AVX512-FP16 was added to GCC.
>>> + AVX512FP16 intrinsics are available [...]
>> So, is it AVX512-FP16 or AVX512FP16?
> Sorry for the confusion, the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108580
--- Comment #6 from postmaster at raasu dot org ---
There is wrong assumption again... Literal "1" is always unsigned as there is
no implicit signed literals, even though there is explicit signed literals...
When somebody writes "-1" it is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108581
--- Comment #1 from saitofuyuki at jamstec dot go.jp ---
Created attachment 54365
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54365=edit
compiler output
command to compile:
% gfortran -O0 -Wall -v -save-temps dtest.f90
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108581
Bug ID: 108581
Summary: wrong assignment on two-rank array with
deferred-length characters
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Sometimes less is more (and our FAQ can use some trimming/updating for
sure).
Pushed.
Gerald
This entry refers to changes in GCC 3.4 and GCC 4.3 which were released
in 2004 and 2008, respectively, and this is hardly a FAQ any more.
---
htdocs/bugs/index.html | 50
Starting to see some trees in the forrest of links that require
updating...
Pushed.
Gerald
libstdc++-v3/ChangeLog:
* doc/xml/manual/documentation_hacking.xml: Move sourceforge.net
links to https.
* doc/html/manual/documentation_hacking.html: Regenerate.
---
gcc/ChangeLog:
* doc/invoke.texi (Instrumentation Options): Update reference to
AddressSanitizer.
---
gcc/doc/invoke.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index a371cd91ef8..6e3f5bf8216 100644
---
gcc/ChangeLog:
* doc/standards.texi: Update Go1 link.
---
gcc/doc/standards.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/doc/standards.texi b/gcc/doc/standards.texi
index d9ee11ccc29..b54502add41 100644
--- a/gcc/doc/standards.texi
+++
Pushed.
Gerald
libstdc++-v3/ChangeLog:
* doc/xml/manual/abi.xml: Update www.open-std.org link to https.
* doc/html/manual/abi.html: Regenerate.
---
libstdc++-v3/doc/html/manual/abi.html | 4 ++--
libstdc++-v3/doc/xml/manual/abi.xml | 4 ++--
2 files changed, 4 insertions(+),
Does anybody have a CI configuration file for gitlab
that does bootstrapping and runs the testsuite?
Martin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108580
--- Comment #5 from Andrew Pinski ---
You are still confused as the assembly code is correct.
Let's start over here.
Take:
char* a = (char*)malloc(1 << bits);
1 << bits is done in int type as the literal 1 has the type of int (because
that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108580
--- Comment #4 from postmaster at raasu dot org ---
I'm not mixing things... The assembly code clearly says it's using 32-bit
shift. Both with 32-bit and 64-bit architectures by default left-hand side of
shift operation is 32 bits (EAX instead
--- Original Message ---
On Monday, January 23rd, 2023 at 3:45 PM, Iain Buclaw
wrote:
>
>
> Excerpts from Lorenzo Salvadore's message of Januar 10, 2023 5:10 pm:
>
> > Hello,
> >
> > Ping https://gcc.gnu.org/pipermail/gcc-patches/2022-November/605685.html
> >
> > I would like to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108580
--- Comment #3 from Andrew Pinski ---
(In reply to postmaster from comment #2)
> If I try to shift to highest bit of signed type, the compiler will reject
> the code and that is correct behaviour. The point here is that left-hand
> side of the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108580
--- Comment #2 from postmaster at raasu dot org ---
If I try to shift to highest bit of signed type, the compiler will reject the
code and that is correct behaviour. The point here is that left-hand side of
the shift operation is by default same
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108579
Andrew Pinski changed:
What|Removed |Added
Keywords||needs-bisection,
|
91 matches
Mail list logo
