https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109169
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109169
--- Comment #5 from Andrew Pinski ---
I suspect the thing you are requesting is having the template keyword as being
optional but I am not sure.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109169
--- Comment #4 from Andrew Pinski ---
You provide a full example of what you want?
Because right now your example your provided does not even compile with msvc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109169
--- Comment #3 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #2)
> There is a defect report in this area of gcc.
Sorry c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109169
--- Comment #2 from Andrew Pinski ---
There is a defect report in this area of gcc.
Hi,
This patch merges the D front-end and run-time library with upstream dmd
5f7552bb28, and standard library with phobos 67a47cf39.
Synchronizing the latest bug fixes in the upcoming v2.103.0 release.
D front-end changes:
- Import dmd v2.103.0-rc.1.
D runtime changes:
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109169
--- Comment #1 from steve02081504 ---
(Corrected code)
```c++
template
struct type_info_t{
//...
template
static constexpr bool can_convert_to=XXX;
//...
};
template
constexpr type_info_ttype_info{};
```
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109169
Bug ID: 109169
Summary: Feature request: Allow omitted template prompts
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
This section of the GCC manual had some issues with lines in the example
overflowing into the right margin of the PDF-format document, but as I
looked at it more closely I also saw that it was full of missing or
incorrect Texinfo markup, too. I've cleaned it up thusly.
-Sandracommit
I noticed when looking at other things last week that there were a whole
bunch of too-long lines overflowing into the right margin in the PDF
version of the GCC manual. This patch fixes some of them. There are
still a whole bunch of especially bad ones in the diagnostic message
formatting
Hi,
When assigning a parameter to a variable, or assigning a variable to
return value with struct type, and the parameter/return is passed
through registers.
For this kind of case, it would be better to use the nature mode of
the registers to move the content for the assignment.
As the example
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109168
--- Comment #1 from Andrew Pinski ---
(In reply to waffl3x from comment #0)
> BTW, should I be selecting the oldest version that a bug occurs or the
> newest version? I observed the behavior all the way back to 10.1, which
> appears to be when
The issue of suboptimal code exists even for integer return value and not just
bool return value. See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103784#c9
So the patch would need to take care of integer return values too.
On 16/03/23 10:50 am, Ajit Agarwal via Gcc-patches wrote:
> Hello All:
Hi,
This patch is fixing an issue about parameter accessing if the
parameter is struct type and passed through integer registers, and
there is floating member is accessed. Like below code:
typedef struct DF {double a[4]; long l; } DF;
double foo_df (DF arg){return arg.a[3];}
On ppc64le, with
on my system with version: g++ (GCC) 13.0.1 20230219
(experimental)
Here is the gcc version on compiler explorer at the time of writing: g++
(Compiler-Explorer-Build-gcc-0c061da91a3657afdb3fac68e4595af685909a1a-binutils-2.38)
13.0.1 20230316 (experimental)
BTW, should I be selecting the oldest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105959
--- Comment #10 from Hans-Peter Nilsson ---
(In reply to David Malcolm from comment #8)
> Note that section 3.1 ("File Format" > "General") specifies:
> "A SARIF log file SHALL be encoded in UTF-8 [RFC3629]."
>
Hi Richard,
在 2023/3/16 18:36, Richard Biener 写道:
> On Thu, Mar 16, 2023 at 10:04 AM HAO CHEN GUI wrote:
>>
>> Hi Richard,
>>
>> 在 2023/3/16 15:57, Richard Biener 写道:
>>> So this is one way around the lack of CSE/PRE of constant operands. I'd
>>> argue that a better spot for this _might_ be LRA
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109167
Kewen Lin changed:
What|Removed |Added
Ever confirmed|0 |1
Target|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109167
Bug ID: 109167
Summary: rs6000: _mm_slli_si128 and _mm_bslli_si128 are
inconsistent in wrapper header
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109166
--- Comment #2 from Andrew Pinski ---
Armv4t does not have smp so the question is how do you think the below is not
atomic? Yes interrupts but that requires more.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109166
--- Comment #1 from Andrew Pinski ---
https://inbox.sourceware.org/gcc-patches/4f596367.2050...@redhat.com/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109166
Bug ID: 109166
Summary: Built-in __atomic_test_and_set does not seem to be
atomic on ARMv4T
Product: gcc
Version: 11.2.1
Status: UNCONFIRMED
Severity: normal
On 3/17/23 02:12, Alejandro Colomar wrote:
> Warn about the following:
>
> char s[3] = "foo";
>
> Initializing a char array with a string literal of the same length as
> the size of the array is usually a mistake. Rarely is the case where
> one wants to create a non-terminated character
Warn about the following:
char s[3] = "foo";
Initializing a char array with a string literal of the same length as
the size of the array is usually a mistake. Rarely is the case where
one wants to create a non-terminated character sequence from a string
literal.
In some cases, for writing
Pushed.
Gerald
---
htdocs/readings.html | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/htdocs/readings.html b/htdocs/readings.html
index 3cdc47a9..6813b84f 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -310,8 +310,8 @@ names.
z/Architecture (S/390)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109165
Bug ID: 109165
Summary: std::hash>::operator() should be
const
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
On Sat, 10 Mar 2018, Segher Boessenkool wrote:
>> It appears this link at atmel.com has been taken down without
>> what appears a replacement, so I applied the patch below.
> Atmel was bought by Microchip some two years ago... Maybe
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109164
--- Comment #3 from Andrew Pinski ---
I am not 100% if this is a front-end issue or a gimple level optimization
issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109164
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
With this the Modula-2 manual -- quite impressive, but the way -- is now
finally reachable from our /onlinedocs page.
Gerald
---
htdocs/onlinedocs/index.html | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/htdocs/onlinedocs/index.html b/htdocs/onlinedocs/index.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109164
Andrew Pinski changed:
What|Removed |Added
Summary|thread_local initialization |thread_local initialization
On Thu, 16 Mar 2023, Gaius Mulley wrote:
>> Does maintainer-scripts/update_web_docs_git require an update to cover
>> Modula-2 and actually build the manual we are now linking to
> Apologies I was going to ask about these links. I've updated the m2
> subtree with target documentation independent
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109164
Bug ID: 109164
Summary: aarch64 thread_local initialization error with
-ftree-pre and -foptimize-sibling-calls
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109163
David Malcolm changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
Hello
There's a typo in the common function attribute docs, "nonnul" which this patch
corrects.
https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#Common-Function-Attributes
gcc/ChangeLog
2023-03-16 Jonny Grant
* doc/extend.texi: correct function attribute typo
---
Snapshot gcc-10-20230316 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/10-20230316/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 10 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105809
--- Comment #6 from CVS Commits ---
The trunk branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:78b3bf0e65072f5fa42a8da43698711220d4f8ef
commit r13-6723-g78b3bf0e65072f5fa42a8da43698711220d4f8ef
Author: Jason Merrill
Date:
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
As in 108242, we need to instantiate in the context of the enclosing
function, not after it's gone.
PR c++/105809
gcc/cp/ChangeLog:
* init.cc (get_nsdmi): Split out...
(maybe_instantiate_nsdmi_init): ...this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108242
--- Comment #8 from CVS Commits ---
The trunk branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:b323f52ccf966800297b0520b9e1d4b3951db525
commit r13-6722-gb323f52ccf966800297b0520b9e1d4b3951db525
Author: Jason Merrill
Date:
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
Here we are trying to do name lookup in a deferred instantiation of t() and
failing to find __func__. tsubst_expr already tries to instantiate members
of local classes, but was failing with the partial instantiation of generic
lambdas.
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
We don't want to call build_offset_ref with an enum.
PR c++/101869
gcc/cp/ChangeLog:
* semantics.cc (finish_qualified_id_expr): Don't try to build a
pointer-to-member if the scope is an enumeration.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101869
--- Comment #5 from CVS Commits ---
The trunk branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:1cc8814098bb46f9fca58a0b831fbf9a8574bdc9
commit r13-6721-g1cc8814098bb46f9fca58a0b831fbf9a8574bdc9
Author: Jason Merrill
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109163
--- Comment #1 from David Malcolm ---
This would also help with one of the requests from a SARIF expert's review of
GCC's output:
https://github.com/oasis-tcs/sarif-spec/issues/531#issuecomment-1181191100
which is that the "version" property
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105959
--- Comment #9 from David Malcolm ---
(In reply to David Malcolm from comment #7)
[...snip...]
> There some variation due to json::object using a hash_map for the key/value
> pairs, which means (annoyingly) it outputs things in arbitrary
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109163
Bug ID: 109163
Summary: SARIF (and other JSON) output files are
non-deterministic
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105959
--- Comment #8 from David Malcolm ---
Note that section 3.1 ("File Format" > "General") specifies:
"A SARIF log file SHALL be encoded in UTF-8 [RFC3629]."
https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html
Though I suppose it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105959
David Malcolm changed:
What|Removed |Added
Last reconfirmed|2023-01-30 00:00:00 |2023-03-16
Ever confirmed|0
on a structure with a C99 flexible array member being nested in
another structure. (PR77650)
"GCC extension accepts a structure containing an ISO C99 "flexible array
member", or a union containing such a structure (possibly recursively)
to be a member of a structure.
There are two situations:
GCC extension accepts the case when a struct with a flexible array member
is embedded into another struct or union (possibly recursively).
__builtin_object_size should treat such struct as flexible size per
-fstrict-flex-arrays.
gcc/c/ChangeLog:
PR tree-optimization/101832
*
Hi, Joseph, Jakub and Sandra,
Could you please review this patch and let me know whether it???s ready
for committing into GCC13?
The fix to Bug PR101832 is an important patch for kernel security
purpose. it's better to be put into GCC13.
===
These are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109159
Marek Polacek changed:
What|Removed |Added
Ever confirmed|0 |1
Keywords|needs-bisection
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109159
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |10.5
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105089
Indu Bhagat changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109159
Andrew Pinski changed:
What|Removed |Added
Status|NEW |UNCONFIRMED
Ever confirmed|1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109159
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109162
Jonathan Wakely changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109162
Bug ID: 109162
Summary: C++23 improvements to std::format
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81323
--- Comment #6 from Andrew Macleod ---
(In reply to Jakub Jelinek from comment #4)
> Or the ranger could do it itself, similarly to how it handles .ASSUME, but
> without actually querying anything but the global range of the return value
> if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109161
Bug ID: 109161
Summary: Bad CTF generated for stub in function scope
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109125
--- Comment #10 from CVS Commits ---
The master branch has been updated by Gaius Mulley :
https://gcc.gnu.org/g:f231bca93ca92f6fd55de6fbe4bf8935f9ec558a
commit r13-6719-gf231bca93ca92f6fd55de6fbe4bf8935f9ec558a
Author: Gaius Mulley
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107630
--- Comment #3 from CVS Commits ---
The master branch has been updated by Gaius Mulley :
https://gcc.gnu.org/g:77924dff144cf934e7a73417d237a99f0d9d66ed
commit r13-6718-g77924dff144cf934e7a73417d237a99f0d9d66ed
Author: Gaius Mulley
Date:
Just to add a bit more color on this one...
It was originally observed (and isolated from)
_ZN11xalanc_1_1027XalanReferenceCountedObject12addReferenceEPS0_ and
reproduces both for AArch64 and RISC-V.
The basic block (annotated with dynamic instructions executed and
percentage of total dynamic
096
```
Output of godbolt's gcc(trunk):
```
# g++ --version
g++
(Compiler-Explorer-Build-gcc-0c061da91a3657afdb3fac68e4595af685909a1a-binutils-2.38)
13.0.1 20230316 (experimental)
# g++ -std=c++20
: In substitution of 'template,
Traits>] rhsBar> void Foo::doNothing(const Foo&)
[with auto [
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38220
--- Comment #10 from anlauf at gcc dot gnu.org ---
(In reply to Jeff Hammond from comment #8)
> For what it's worth, ISO/IEC DIS 1539-1:2022 (E) now contains the following:
>
> All standard procedures in the intrinsic module ISO_C_BINDING, other
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109159
Bug ID: 109159
Summary: explicit constructor is used in copy-initialization
Product: gcc
Version: 12.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106188
Arsen Arsenović changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106713
Arsen Arsenović changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
8-byte modes should be processed only for TARGET_MMX_WITH_SSE.
gcc/ChangeLog:
* config/i386/i386-expand.cc (expand_vec_perm_pblendv):
Handle 8-byte modes only with TARGET_MMX_WITH_SSE.
(expand_vec_perm_2perm_pblendv): Ditto.
Bootstrapped and regression tested on x86_64-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105809
Jason Merrill changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108242
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105554
--- Comment #15 from Jakub Jelinek ---
Created attachment 54686
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54686=edit
gcc13-pr105554.patch
This untested patch seems to work.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109030
--- Comment #5 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:31cdfdef04701e10cffcec4578b2337684f0e4bc
commit r13-6716-g31cdfdef04701e10cffcec4578b2337684f0e4bc
Author: Patrick Palka
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105554
--- Comment #14 from Jakub Jelinek ---
So, I have tried
--- gcc/cgraphclones.cc.jj 2023-02-24 11:05:19.704595633 +0100
+++ gcc/cgraphclones.cc 2023-03-16 19:12:30.452503051 +0100
@@ -1094,6 +1094,15 @@
> From: Hans-Peter Nilsson
> Date: Thu, 16 Mar 2023 19:25:05 +0100
> That doesn't seem like a good idea. At a glance the
> *testcode* will be simpler, but the patch will be slightly
> larger
Bah, s/but the patch will be slightly larger/and the patch
will certainly be smaller, but because less
On Thu, 2023-03-16 at 19:25 +0100, Hans-Peter Nilsson wrote:
> > From: David Malcolm
> > Date: Thu, 16 Mar 2023 13:55:48 -0400
>
> > On Thu, 2023-03-09 at 19:56 +0100, Hans-Peter Nilsson wrote:
> > > It's not obvious to me whether considered best to include or
> > > exclude these tests that
> On Mar 16, 2023, at 12:53 PM, Jakub Jelinek wrote:
>
> On Thu, Mar 16, 2023 at 04:38:41PM +, Qing Zhao via Gcc-patches wrote:
>>> NO. We have this debate every few years and such.
>>
>> So, what’s the major reason we keep the default that is not IEEE754
>> compliant from the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109140
Sam James changed:
What|Removed |Added
CC||davem at davemloft dot net
--- Comment #11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100288
Patrick Palka changed:
What|Removed |Added
Keywords||error-recovery,
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109145
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #9 from Andrew Pinski
> From: David Malcolm
> Date: Thu, 16 Mar 2023 13:55:48 -0400
> On Thu, 2023-03-09 at 19:56 +0100, Hans-Peter Nilsson wrote:
> > It's not obvious to me whether considered best to include or
> > exclude these tests that depend on structure layout details.
> > If excluding, the obvious alternative
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100288
--- Comment #13 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:c630157fd01140dbce120c1409c413a97dc17104
commit r13-6715-gc630157fd01140dbce120c1409c413a97dc17104
Author: Patrick Palka
Date:
ping
From: Wilco Dijkstra
Sent: 23 February 2023 15:11
To: GCC Patches
Cc: Richard Sandiford ; Kyrylo Tkachov
Subject: [PATCH] libatomic: Fix SEQ_CST 128-bit atomic load [PR108891]
The LSE2 ifunc for 16-byte atomic load requires a barrier before the LDP -
without it, it effectively has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109145
--- Comment #8 from seurer at gcc dot gnu.org ---
Alas, yes. This system is quite old and not being updated any more. It
hopefully will be retired soon.
This probably isn't a big deal and as far as I am concerned can be ignored.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105554
--- Comment #13 from Jakub Jelinek ---
A lot of ipa passes use push_cfun:
grep push_cfun ipa*.cc
ipa-fnsummary.cc: push_cfun (DECL_STRUCT_FUNCTION (node->decl));
ipa-fnsummary.cc: push_cfun (DECL_STRUCT_FUNCTION (node->decl));
On Thu, 2023-03-09 at 19:56 +0100, Hans-Peter Nilsson wrote:
> It's not obvious to me whether considered best to include or
> exclude these tests that depend on structure layout details.
> If excluding, the obvious alternative to this patch is then
> to add a top one-liner (to dg-skip-if the test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108636
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108636
--- Comment #7 from CVS Commits ---
The releases/gcc-10 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:d640e435f156d8f825bf95c2164053b4a3a7b682
commit r10-11253-gd640e435f156d8f825bf95c2164053b4a3a7b682
Author: Jonathan
On Thu, 16 Mar 2023 at 17:45, oszibarack korte via Gcc wrote:
>
> *An unsolved problem for more than a decade!*
> *Dear GNU Compiler Collection development team!*
>
> *There is a problem with the gcc and g++ compilers for Linux operating
> systems!*
> *Here are 3 pieces of C and 3 pieces of C++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109145
--- Comment #7 from Jakub Jelinek ---
So, I think we can either use:
2023-03-16 Jakub Jelinek
PR testsuite/109145
* gcc.dg/tree-ssa/forwprop-39.c (CMPLXF): Define if not defined.
---
On Thu, Mar 16, 2023 at 10:46 AM oszibarack korte via Gcc
wrote:
>
> *An unsolved problem for more than a decade!*
> *Dear GNU Compiler Collection development team!*
>
> *There is a problem with the gcc and g++ compilers for Linux operating
> systems!*
> *Here are 3 pieces of C and 3 pieces of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109157
anlauf at gcc dot gnu.org changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
*An unsolved problem for more than a decade!*
*Dear GNU Compiler Collection development team!*
*There is a problem with the gcc and g++ compilers for Linux operating
systems!*
*Here are 3 pieces of C and 3 pieces of C++ source code.*
*- Please compile them on any LINUX!- Run it!- Compare the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109145
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108685
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109145
--- Comment #5 from seurer at gcc dot gnu.org ---
The excess error is:
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/tree-ssa/forwprop-39.c: In
function 'foo':
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109145
--- Comment #4 from seurer at gcc dot gnu.org ---
Created attachment 54684
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54684=edit
Preprocessed file
Attached file from this command
/home/seurer/gcc/git/build/gcc-test/gcc/xgcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109140
--- Comment #10 from Mikael Pettersson ---
A bisect between 4.6.4 (good) and 4.7.4 (bad) found:
1f9ed162eb30f1b40b65d164b3a40ac78e1f006e is the first bad commit
commit 1f9ed162eb30f1b40b65d164b3a40ac78e1f006e
Author: David S. Miller
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101869
Jason Merrill changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91133
Jason Merrill changed:
What|Removed |Added
Status|ASSIGNED|SUSPENDED
Assignee|jason at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109158
Bug ID: 109158
Summary: arm: errors when mixing
__attribute__((pcs("aapcs-vfp"))) with +nofp
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: minor
1 - 100 of 228 matches
Mail list logo
