https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99145
--- Comment #4 from Vittorio Zecca ---
(In reply to Jerry DeLisle from comment #3)
> Initially it is creating the very large string in the frontend passes and
> then via resolution and translation phases, and finally into the middle-end
> and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99147
--- Comment #5 from Vittorio Zecca ---
I ran the testsuite against the proposed fix and it was successful, no
sanitizer errors in symbol.c.
Only remaining error as in bug 99148.
For R6+ target, it allows to configure gcc to use compact branches only.
gcc/ChangeLog:
* config.gcc: add -with-compact-branches=policy build option.
* doc/install.texi: Likewise.
---
gcc/ChangeLog| 5 +
gcc/config.gcc | 12 +++-
gcc/doc/install.texi |
For MIPSr6, we may wish to use compact-branches only.
Currently, we have to use `always' option, while it is mark as conflict
with pre-R6.
cc1: error: unsupported combination: ‘mips32r2’ -mcompact-branches=always
Just ignore -mcompact-branches=always for pre-R6.
This patch also defines
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99134
--- Comment #1 from CVS Commits ---
The master branch has been updated by Ilya Leoshkevich :
https://gcc.gnu.org/g:b6e446cb58183557a5a5d87dc866aae9613544f8
commit r11-7310-gb6e446cb58183557a5a5d87dc866aae9613544f8
Author: Ilya Leoshkevich
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99178
Bug ID: 99178
Summary: Emit .debug_names
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee:
On Fri, 19 Feb 2021, Patrick McGehearty via Gcc-patches wrote:
> > Here you're properly computing the mapping from mode to float.h macro
> > prefix (though I think "modename" is a confusing name for the variable
> > used for float.h macro prefixes; to me, "modename" suggests the names such
> > as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99173
--- Comment #2 from H.J. Lu ---
Created attachment 50228
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50228=edit
A patch
Try this.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98512
Martin Sebor changed:
What|Removed |Added
Target Milestone|11.0|12.0
--- Comment #6 from Martin Sebor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98465
Martin Sebor changed:
What|Removed |Added
Target Milestone|11.0|12.0
--- Comment #32 from Martin Sebor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87489
--- Comment #16 from Martin Sebor ---
The test case in
https://gcc.gnu.org/pipermail/gcc-patches/2021-February/565564.html shows that
running the -Wnonnull pass later, after FRE, allows the warning to detect the
bug in the following test case:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99176
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99176
Marek Polacek changed:
What|Removed |Added
Summary|GCC rejects const_cast of |[8/9/10/11 Regression] GCC
Comments inline
On 2/19/2021 3:27 PM, Joseph Myers wrote:
On Tue, 2 Feb 2021, Patrick McGehearty via Gcc-patches wrote:
if (mode == TYPE_MODE (double_type_node))
- ; /* Empty suffix correct. */
+ {
+ ; /* Empty suffix correct. */
+
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99177
Bug ID: 99177
Summary: FAIL: g++.dg/modules/adl-1 -std=c++17 link
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99176
Bug ID: 99176
Summary: GCC rejects const_cast of null pointer in constant
expressions
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99175
Bug ID: 99175
Summary: FAIL: g++.dg/modules/bad-mapper-1.C -std=c++17 (test
for errors, line )
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99173
--- Comment #1 from seurer at gcc dot gnu.org ---
There are actually a bunch more. Here's the full list:
FAIL: c-c++-common/attr-retain-5.c -Wc++-compat (test for excess errors)
FAIL: c-c++-common/attr-retain-5.c -std=gnu++14 (test for
Snapshot gcc-9-20210219 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/9-20210219/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 9 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99153
--- Comment #2 from Nathan Sidwell ---
// B_a.ii
template
struct pair
{
inline void Frob ();
};
// B_b.ii
import "./B_a.ii"
template
inline void pair<_T1>::Frob()
{ }
./cc1plus -quiet -std=c++20 -fmodule-header -fpreprocessed B_a.ii &&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99174
Bug ID: 99174
Summary: [modules] ICE with recursive inclusion of header-unit
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99173
Bug ID: 99173
Summary: new test case c-c++-common/attr-retain-5.c added in
r11-7284 fails
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99156
--- Comment #2 from zhan3299 at purdue dot edu ---
(In reply to Martin Liška from comment #1)
> Yes, I can confirm the issue. Thanks for the report.
Many thanks for your prompt reply. Additionally, I have to give credit to
Richard Smith for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98741
Nathan Sidwell changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98741
--- Comment #2 from CVS Commits ---
The master branch has been updated by Nathan Sidwell :
https://gcc.gnu.org/g:14886cbe300c144a4390245d0515cdf28fc5f68f
commit r11-7307-g14886cbe300c144a4390245d0515cdf28fc5f68f
Author: Nathan Sidwell
Date:
One of the very strong invariants in modules is that module numbers are
allocated such that (other than the current TU), all imports have lesser
module numbers, and also that the binding vector is only appended to
with increasing module numbers. This broke down when module-directives
became
On Tue, 2 Feb 2021, Patrick McGehearty via Gcc-patches wrote:
> if (mode == TYPE_MODE (double_type_node))
> - ; /* Empty suffix correct. */
> + {
> + ; /* Empty suffix correct. */
> + memcpy (modename, "DBL", 4);
> + }
> else if (mode
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
Dear all,
we should not clobber the pointer in case of an allocatable scalar being
an intent(out) dummy argument to a procedure.
Regtested on x86_64-pc-linux-gnu.
OK for master? Since this is a regression, also for backports to 10/9?
Thanks,
Harald
PR fortran/99169 - Do not clobber
On Thu, Feb 18, 2021 at 10:44:14PM -0500, Michael Meissner wrote:
> On Wed, Feb 17, 2021 at 06:09:39PM -0600, Segher Boessenkool wrote:
> > Why test a p10 patch on a p8?
>
> Well it is just a code gen patch, so I can test it on any system, even an
> x86_64 with a cross compiler. Given that right
On Fri, 2021-02-19 at 11:16 +0100, Andrea Corallo wrote:
> David Malcolm via Gcc-patches writes:
>
> > I tried several approaches to fixing this; this seemed the
> > least invasive.
>
> Hi Dave,
>
> thanks for fixing this.
>
> I do have a trivial question: are we guaranteed that the
Hi!
On Fri, Feb 19, 2021 at 11:06:16AM +0800, Kewen.Lin wrote:
> on 2021/2/19 上午2:33, Segher Boessenkool wrote:
> > Is there a PR you should mention here?
>
> I thought this is trivial so didn't file one upstream PR. I did a
> searching in upstream bugzilla, PR93453 looks similar but different.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99172
Bug ID: 99172
Summary: Build failure with slibtool and vtv
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98686
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jerry DeLisle :
https://gcc.gnu.org/g:dfa2f821c18b7e926b5f5d6e394a0c915937db5e
commit r11-7306-gdfa2f821c18b7e926b5f5d6e394a0c915937db5e
Author: Jerry DeLisle
Date:
This patch updates libgo to the final Go 1.16 release. Bootstrapped
and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline.
Ian
c89b42d3b9d76dedb35e8478913ddf5367f3b5e6
diff --git a/gcc/go/gofrontend/MERGE b/gcc/go/gofrontend/MERGE
index eed9ce01905..217bdd55f1d 100644
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99171
Bug ID: 99171
Summary: [10 Regression] Optional procedure call inside Open MP
parallel loop produces Segmentation Fault
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97366
--- Comment #8 from Vladimir Makarov ---
I've tried different approaches to fix it. The best patch I have now is in the
attachment.
Unfortunately, the best patch results in two new failures on ppc64 (other
patches are even worse):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96264
seurer at gcc dot gnu.org changed:
What|Removed |Added
Status|RESOLVED|REOPENED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97366
--- Comment #7 from Vladimir Makarov ---
Created attachment 50225
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50225=edit
A candidate patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
--- Comment #3 from anlauf at gcc dot gnu.org ---
A conservative solution simply disables the clobber:
diff --git a/gcc/fortran/trans-expr.c b/gcc/fortran/trans-expr.c
index 103cb31c664..ce7bfaa89e8 100644
--- a/gcc/fortran/trans-expr.c
+++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99170
--- Comment #1 from Rémi Galan Alfonso ---
Created attachment 50224
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50224=edit
preprocessed file
... And with the correct preprocessed file this time, apologies for my mistake.
c-9 CXX=g++-9 --enable-languages=c,c++,fortran,lto,objc
--no-create --no-recursion
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 11.0.0 20210219 (experimental) (GCC)
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-std=c++20' '-fmodules-ts' '-c'
'-shared-libgcc' '-mtune=generic' '
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
--- Comment #2 from anlauf at gcc dot gnu.org ---
Note/workaround: the {CLOBBER} disappears if the argument to set_i is declared
INOUT instead of OUT.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Known to work||8.4.1
Priority|P3
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the French team of translators. The file is available at:
https://translationproject.org/latest/gcc/fr.po
(This file,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96264
Peter Bergner changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99147
--- Comment #4 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:af027826292351218785f893d1c42fe28ae3ed9f
commit r11-7303-gaf027826292351218785f893d1c42fe28ae3ed9f
Author: Harald Anlauf
Date:
Hello
Sorry for taking so long in replying.
On 29/01/2021 3:03 pm, Jakub Jelinek wrote:
It can also crash if team is NULL, which will happen any time
this is called outside of a parallel. Just try (should go into testsuite
too):
#include
int
main ()
{
omp_event_handle_t ev;
#pragma
On 2/19/21 2:48 AM, Franz Sirl wrote:
Am 2021-02-01 um 01:31 schrieb Martin Sebor via Gcc-patches:
The initial -Wnonnull implementation in the middle end took place
too late in the pipeline (just before expansion), and as a result
was prone to false positives (bug 78817). In an attempt to
On Fri, 19 Feb 2021, Project Revolution via Gcc wrote:
> Gentlemen: this was fixed, although it's a bit of an odd solution. We
> had to combine both -mno-explicit-relocs and -mno-split-addresses, even
> though per the MIPS compiler documentation explicit relocs supersedes
> the split addresses
On 2/18/21 8:51 PM, Jeff Law wrote:
On 2/18/21 7:23 PM, Martin Sebor wrote:
The fix for PR 97172 that removes non-constant VLA bounds from
attribute access is incomplete: it inadvertently removes the bounds
corresponding to just the first VLA argument, and not from subsequent
arguments.
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97172
--- Comment #29 from CVS Commits ---
The master branch has been updated by Martin Sebor :
https://gcc.gnu.org/g:3599ecb6a0145a428def5314d2d67d2e5a88f3c4
commit r11-7301-g3599ecb6a0145a428def5314d2d67d2e5a88f3c4
Author: Martin Sebor
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99159
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99166
Nathan Sidwell changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
When successfully reading a module CMI, the user gets no indication of
where that CMI was located. I originally didn't consider this a problem
-- the read was successful after all. But it can make it difficult to
interact with build systems, particularly when caching can be involved.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
Bug ID: 99169
Summary: Segfault when passing allocatable scalar into
intent(out) dummy argument
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98890
--- Comment #6 from Jerry DeLisle ---
I should have noted in the above case, if we remove the parens on line 5,
k = f1 is rejected.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98210
Jozef Lawrynowicz changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|REOPENED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99146
Tobias Burnus changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99010
Tobias Burnus changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99010
--- Comment #2 from CVS Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:f86e187e12db14ad1cced26b9f8aafb06498e208
commit r11-7299-gf86e187e12db14ad1cced26b9f8aafb06498e208
Author: Tobias Burnus
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99146
--- Comment #1 from CVS Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:72d91d6cd41f2987339a98c2c64f70b3850f4e0b
commit r11-7298-g72d91d6cd41f2987339a98c2c64f70b3850f4e0b
Author: Tobias Burnus
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98875
--- Comment #5 from Mark Wielaard ---
https://gcc.gnu.org/pipermail/gcc-patches/2021-February/565587.html
* gcc-11/changes.html (General Improvements): Add a section on
the DWARF version 5 default.
---
htdocs/gcc-11/changes.html | 30 ++
1 file changed, 30 insertions(+)
diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91191
--- Comment #8 from Andrew Macleod ---
(In reply to Jeffrey A. Law from comment #7)
> If you're V_C_E-ing to a narrower type, you just ignore the bits outside the
> target type, it's a lot like a narrowing subreg in the RTL world.
>
> I don't
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99168
--- Comment #1 from zhan3299 at purdue dot edu ---
If we resolved the conflicts on "aligned", it would behave normally. I feel
like the ASAN is confused by the "aligned" somehow.
Should it have thrown some warnings?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98890
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99168
Bug ID: 99168
Summary: inconsistent behavior on -O0 and -O2 with ASAN on
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
Hi Jerry,
On 17.02.21 04:02, Jerry DeLisle wrote:
Attached patch adds to checks. In the case of IMPLICIT typing it
checks to see if the objects listed in the NAMELIST have defined types
andf if not, sets them to the default implicit types.
In the case of IMPLICIT NONE, the types are required
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96264
--- Comment #13 from seurer at gcc dot gnu.org ---
Thanks, that did fix it on trunk.
Pushed to master as obvious.
Martin
gcc/ChangeLog:
PR translation/99167
* params.opt: Fix typo.
---
gcc/params.opt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/params.opt b/gcc/params.opt
index a4e1ac0e88e..0dd9ac406eb 100644
--- a/gcc/params.opt
+++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99167
Martin Liška changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99167
--- Comment #2 from CVS Commits ---
The master branch has been updated by Martin Liska :
https://gcc.gnu.org/g:c8d13835638ff82f3ba7bfb0a5c2f597851dfb5a
commit r11-7297-gc8d13835638ff82f3ba7bfb0a5c2f597851dfb5a
Author: Martin Liska
Date: Fri
On 2/19/21 1:33 AM, Tobias Burnus wrote:
On 09.02.21 12:52, Tobias Burnus wrote:
Hi all, hi Thomas,
On 02.02.21 18:15, Tobias Burnus wrote:
I think I will do a combination: If 'identical' is true, I think I
cannot remove it. If it is false, it can be identical or nonoverlapping
– which makes
On 2/19/21 8:00 AM, Tobias Burnus wrote:
In this example, the formal argument is a derived type
and not a class – hence, there is an ICE.
OK for the trunk?
This is OK, could you also check 89219 and 81499 and see if these are
the same or similar.
Much appreciated.
Jerry
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99167
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2021-02-19
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99145
--- Comment #3 from Jerry DeLisle ---
Initially it is creating the very large string in the frontend passes and then
via resolution and translation phases, and finally into the middle-end and back
end phases where it I am guessing the optimizers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99167
Bug ID: 99167
Summary: typo in params.opt: accesse
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: translation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98890
--- Comment #4 from Tobias Burnus ---
Related issue but without an ICE:
contains
integer function f1()
!f2 = 1 ! gives an error as expected
j = f2! accepted; cast of function addr to integer(kind=4)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99157
--- Comment #3 from Hau Hsu ---
Here are some more info.
This check determines whether macro __ARM_FEATURE_CMSE is set to 3,
and affects CMSE support for function cmse_check_address_range():
void *
__attribute__ ((warn_unused_result))
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98875
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|unassigned at gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99157
--- Comment #2 from Hau Hsu ---
Created attachment 50221
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50221=edit
libgcc objdump result for gcc-7 and gcc-10
In this example, the formal argument is a derived type
and not a class – hence, there is an ICE.
OK for the trunk?
Tobias
-
Mentor Graphics (Deutschland) GmbH, Arnulfstrasse 201, 80634 München
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Frank
Thürauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99147
--- Comment #3 from Vittorio Zecca ---
I changed symbol.c as per your suggestion and now the address
sanitized gfortran compiles fine.
Now I am going to check it against the testsuite.
Results tomorow.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99165
Martin Liška changed:
What|Removed |Added
Summary|[11 Regression] ICE in |ICE in verify_dominators,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99165
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98389
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98389
--- Comment #3 from Jonathan Wakely ---
(In reply to seurer from comment #0)
> 3 incompatible symbols
> 0
> _ZSt8to_charsPcS_g
> std::to_chars(char*, char*, __float128)
It took me a while to realise that these symbols are not __float128,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99156
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2021-02-19
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99137
--- Comment #5 from Tobias Burnus ---
Iff it is decided that it is invalid code, the following patch rejects it:
https://gcc.gnu.org/pipermail/gcc-patches/2021-February/565576.html
(I forgot to reload the PR before posting.)
On 2021-02-19 5:53 a.m., Andre Vieira (lists) wrote:
Hi,
This patch makes sure that allocno copies are not created for
unordered modes. The testcases in the PR highlighted a case where an
allocno copy was being created for:
(insn 121 120 123 11 (parallel [
(set (reg:VNx2QI 217)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98967
Nathan Sidwell changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |nathan at gcc dot
gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99164
Ian Lance Taylor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
Hello!
Thank you for the information. I am also quite confused with this issue. I
note that it seems that given the following statement:
m_pstSwtmrCBArray.27_1 = m_pstSwtmrCBArray;
where m_pstSwtmrCBArray is a global variable (a pointer). When passing a
tree pointer `v` referring to
Ps. The code in comment is needed, but was commented out due to the early free
issue described in the patch.
Thanks,
Tamar
> -Original Message-
> From: Tamar Christina
> Sent: Friday, February 19, 2021 2:42 PM
> To: gcc-patches@gcc.gnu.org
> Cc: nd ; rguent...@suse.de
> Subject:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98357
Andrew Macleod changed:
What|Removed |Added
CC||aldyh at redhat dot com,
Hi Richi,
The attached testcase ICEs due to a couple of issues.
In the testcase you have two SLP instances that share the majority of their
definition with each other. One tree defines a COMPLEX_MUL sequence and the
other tree a COMPLEX_FMA.
The ice happens because:
1. the refcounts are wrong,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99166
Bug ID: 99166
Summary: [modules] Unable to determine where CMI is being found
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98389
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |ASSIGNED
1 - 100 of 166 matches
Mail list logo
