https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95284
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |11.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14907
--- Comment #5 from H.J. Lu ---
(In reply to Nicholas Miell from comment #4)
> This also occurs on AMD64 without any special attributes (the ABI passes
> params in registers already).
>
> When compiling:
> extern char c2(char);
> char c1(char c)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117265
--- Comment #15 from Andrew Pinski ---
Maybe what you want is really a builtin does the load/store and the ability to
output the register # that the address is formed into instead of this
inline-asm. This might be better than what you are asking
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112716
Sam James changed:
What|Removed |Added
Last reconfirmed||2024-10-27
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98171
David Edelsohn changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117313
Andrew Pinski changed:
What|Removed |Added
Attachment #59452|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117313
--- Comment #3 from Sam James ---
(In reply to Andrew Pinski from comment #1)
> Created attachment 59452 [details]
> Reduced testcase
This is rejected by GCC 14:
/tmp/f.c:2:23: error: flexible array member in a struct with no named members
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117266
--- Comment #16 from H. Peter Anvin ---
Well, if that is the way you feel about it. It is certainly different from the
messages we get in other situations, so it is a bit confusing to me.
It isn't *that* unusual that you know a priori that the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117311
--- Comment #3 from H. Peter Anvin ---
It does, in fact, work just fine under -O0, although it will redundantly
manifest the frame pointer in a different register (which is not a problem.)
Now, it would seem to me that if this *isn't* something
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117313
--- Comment #1 from Andrew Pinski ---
Created attachment 59452
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59452&action=edit
Reduced testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117313
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-10-27
Status|UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117312
--- Comment #2 from H. Peter Anvin ---
I did state that the current kernel ABI doesn't *currently* use the red zone.
However, in the future, FRED exception handling *would* allow the kernel to use
the red zone.
There isn't really a good alterna
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117266
--- Comment #15 from Andrew Pinski ---
(In reply to H. Peter Anvin from comment #14)
> A bigger, philosophical question: we are always told that builtins are
> better for the compiler than inline assembly, as it gives the compiler more
> informa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117313
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |15.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117311
Andrew Pinski changed:
What|Removed |Added
Resolution|WONTFIX |INVALID
--- Comment #2 from Andrew Pins
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117311
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117312
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117265
--- Comment #12 from H. Peter Anvin ---
Certainly. This is *not* only used by copy_*_user (or {get,put}_user for that
matter), here is an example from msr.h:
static inline unsigned long long native_read_msr_safe(unsigned int msr,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117313
Bug ID: 117313
Summary: [15 regression] ICE when building linux-6.11.5
(output_constructor_regular_field, at varasm.cc:5672)
Product: gcc
Version: 15.0
Status: UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117009
Andrew Pinski changed:
What|Removed |Added
Attachment #59448|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117265
--- Comment #14 from H. Peter Anvin ---
Note: comment 13 is not intended to be rhetorical but is a genuine question.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117265
--- Comment #13 from H. Peter Anvin ---
When you say "should be done in an exceptional way", could you please clarify
what you mean? I'm not sure I follow you there? Are you saying we should be
asking for compiler support?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117266
H. Peter Anvin changed:
What|Removed |Added
Summary|RFE: builtins for N*N -> 2N |RFE: builtin 2N/N -> N
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117312
Bug ID: 117312
Summary: RFE: x86 (and perhaps others): inline assembly:
"red-zone" clobber
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117311
Bug ID: 117311
Summary: Documentation request: __builtin_frame_address(0) and
inline assembly
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: norma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117265
--- Comment #10 from Andrew Pinski ---
Your example is not a full example on how you use _ASM_EXTABLE_TYPE_REG .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117265
--- Comment #11 from Andrew Pinski ---
Plus your example is only for copy_{to,from}_user which itself is an
exceptional part of the kernel and should be done in an exceptional way in the
first place.
Do you have other examples that is not from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117265
--- Comment #9 from H. Peter Anvin ---
Created attachment 59450
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59450&action=edit
Proposed assembly header implementation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117265
--- Comment #8 from H. Peter Anvin ---
Created attachment 59449
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59449&action=edit
Current code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117265
--- Comment #7 from H. Peter Anvin ---
I have included a concrete example from the Linux kernel (with other parts of
the code stripped for clarity.)
The file asm_header.s shows how it could be implemented as an assembly header.
As you can see,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117310
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117310
Bug ID: 117310
Summary: Unnecessary zero-extension for tailcall
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117009
--- Comment #2 from Andrew Pinski ---
Created attachment 59448
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59448&action=edit
Patch which I am testing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117300
--- Comment #10 from Andrew Pinski ---
(In reply to H.J. Lu from comment #9)
> Created attachment 59447 [details]
> A patch
>
> This seems to work.
This looks good. Are you going to submit it? If so please add:
Co-authored-by: Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117300
--- Comment #9 from H.J. Lu ---
Created attachment 59447
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59447&action=edit
A patch
This seems to work.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117282
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117308
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117304
Zdenek Sojka changed:
What|Removed |Added
Summary|ICE: in emit_move_insn, at |ICE: in emit_move_insn, at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62230
Eric Botcazou changed:
What|Removed |Added
Status|NEW |RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117308
--- Comment #3 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #2)
> (In reply to Thomas Kieß from comment #0)
> > the current implementation limits overview
> > (https://gcc.gnu.org/onlinedocs/gcc-14.2.0/cpp/Implementation-li
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117308
--- Comment #2 from Jonathan Wakely ---
(In reply to Thomas Kieß from comment #0)
> the current implementation limits overview
> (https://gcc.gnu.org/onlinedocs/gcc-14.2.0/cpp/Implementation-limits.html)
N.B. this page is for cpp the C preproce
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117309
--- Comment #2 from Madarpok . ---
(In reply to Andrew Pinski from comment #1)
> Well c++23 was only published within the last month.
Hmm, fair enough. -std=c++2b has been supported for quite a while, but I see
your point.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117308
--- Comment #1 from Jonathan Wakely ---
I don't think there is any particular limit, it's only limited by your
available RAM when compiling. You will probably experience unacceptably slow
compile times long before you reach a physical limit, but
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117309
--- Comment #3 from Jonathan Wakely ---
(In reply to Andrew Pinski from comment #1)
> Well c++23 was only published within the last month.
Within the last week!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64556
--- Comment #3 from simon at pushface dot org ---
Agreed, fixed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117234
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117234
--- Comment #5 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:5596572b6bf72031de888301ebfe8e984df04dc9
commit r15-4698-g5596572b6bf72031de888301ebfe8e984df04dc9
Author: Andrew Pinski
Date: Sa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117007
--- Comment #6 from Steven Munroe ---
I am starting to see pattern and wonder if the compiler is confused by assuming
the sihft count must match the width/type of the shift/rotate target.
This is implied all the way back to the Altivec-PIM and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117309
Andrew Pinski changed:
What|Removed |Added
Component|web |c++
--- Comment #1 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117309
Bug ID: 117309
Summary: [Docs] C++23 is not mentioned on the "supported
standards" doc page
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18765
--- Comment #6 from Eric Botcazou ---
The key is of course the declaration of the "boolean" subtype, so probably:
diff --git a/gcc/ada/sem_ch6.adb b/gcc/ada/sem_ch6.adb
index 8cf191d751b..9c02ad6ff4f 100644
--- a/gcc/ada/sem_ch6.adb
+++ b/gcc/ad
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117007
Steven Munroe changed:
What|Removed |Added
Attachment #59323|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116979
--- Comment #9 from Paul Caprioli ---
I would like to offer two suggestions for your consideration:
1. For the reason of improving accuracy, the mul_fma code should be generated
for complex operator* regardless of how the flag -ffp-contract is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98171
Eric Botcazou changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #2 from Eric Botcazo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=15819
Eric Botcazou changed:
What|Removed |Added
CC||chrisp_42 at bigpond dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38493
Eric Botcazou changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106031
Eric Botcazou changed:
What|Removed |Added
Status|NEW |RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37309
Eric Botcazou changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82746
Eric Botcazou changed:
What|Removed |Added
Target Milestone|--- |15.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106169
Eric Botcazou changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117234
Andrew Pinski changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62042
Eric Botcazou changed:
What|Removed |Added
Target Milestone|--- |15.0
Assignee|unassigned at gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17321
--- Comment #5 from Eric Botcazou ---
The error is still missing.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99358
Eric Botcazou changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95664
Eric Botcazou changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82639
Eric Botcazou changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90958
Eric Botcazou changed:
What|Removed |Added
Target Milestone|--- |12.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93702
Eric Botcazou changed:
What|Removed |Added
Last reconfirmed|2023-05-11 00:00:00 |2024-10-26
--- Comment #2 from Eric Botc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32318
Eric Botcazou changed:
What|Removed |Added
CC||bib_aab at hotmail dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90051
Eric Botcazou changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89178
Eric Botcazou changed:
What|Removed |Added
Target Milestone|--- |15.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71674
Eric Botcazou changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89742
Eric Botcazou changed:
What|Removed |Added
Last reconfirmed|2023-05-11 00:00:00 |2024-10-26
--- Comment #2 from Eric Botc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89609
Eric Botcazou changed:
What|Removed |Added
Last reconfirmed|2019-03-09 00:00:00 |2024-10-26
--- Comment #2 from Eric Botc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78066
Eric Botcazou changed:
What|Removed |Added
Target Milestone|--- |9.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89159
Eric Botcazou changed:
What|Removed |Added
Last reconfirmed|2023-05-11 00:00:00 |2024-10-26
--- Comment #2 from Eric Botc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82638
Eric Botcazou changed:
What|Removed |Added
Target Milestone|--- |9.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87170
Eric Botcazou changed:
What|Removed |Added
Last reconfirmed|2023-05-11 00:00:00 |2024-10-26
--- Comment #2 from Eric Botc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82529
Eric Botcazou changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83188
Eric Botcazou changed:
What|Removed |Added
Last reconfirmed|2023-05-11 00:00:00 |2024-10-26
--- Comment #2 from Eric Botc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84320
Eric Botcazou changed:
What|Removed |Added
Last reconfirmed|2018-02-12 00:00:00 |2024-10-26
--- Comment #2 from Eric Botc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84198
Eric Botcazou changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81919
Eric Botcazou changed:
What|Removed |Added
Status|NEW |RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83310
Eric Botcazou changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66162
Eric Botcazou changed:
What|Removed |Added
Target Milestone|--- |15.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82637
Eric Botcazou changed:
What|Removed |Added
Target Milestone|--- |9.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81328
Eric Botcazou changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|REOPENED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79445
Eric Botcazou changed:
What|Removed |Added
Target Milestone|--- |10.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77793
Eric Botcazou changed:
What|Removed |Added
Target Milestone|--- |10.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72740
Eric Botcazou changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78175
Eric Botcazou changed:
What|Removed |Added
Last reconfirmed|2016-11-03 00:00:00 |2024-10-26
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68179
Eric Botcazou changed:
What|Removed |Added
Last reconfirmed|2015-11-03 00:00:00 |2024-10-26
--- Comment #6 from Eric Botc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69926
Eric Botcazou changed:
What|Removed |Added
Last reconfirmed|2016-02-28 00:00:00 |2024-10-26
--- Comment #5 from Eric Botc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70015
Eric Botcazou changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #3 from Eric Botcazo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116613
--- Comment #34 from Kamil Dudka ---
(In reply to David Malcolm from comment #33)
> Note that the "2.2-prerelease" stuff does almost nothing at this stage and
> is experimental; you should probably leave "version" unset so that it uses
> the def
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68171
Eric Botcazou changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66608
Eric Botcazou changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62193
Eric Botcazou changed:
What|Removed |Added
Summary|There is a bug in the Ada |some Ada time functions
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117145
uecker at gcc dot gnu.org changed:
What|Removed |Added
Attachment #59404|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62122
Eric Botcazou changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
1 - 100 of 208 matches
Mail list logo