Hi Mike,
on 2022/12/7 14:44, Michael Meissner wrote:
> On Tue, Dec 06, 2022 at 05:36:54PM +0800, Kewen.Lin wrote:
>> Hi Mike,
>>
>> Thanks for fixing this!
>>
>> Could you help to elaborate why we need to disable it during libgcc building?
>
> When you are building libgcc, you are building the
On 07.12.22 08:10, Thomas Schwinge wrote:
Hi!
On 2022-12-07T07:04:10+0100, Sebastian Huber
wrote:
On 06.12.22 22:06, Thomas Schwinge wrote:
I suppose I just fail to see some detail here, but:
On 2022-11-21T08:25:25+0100, Sebastian
Huber wrote:
gcc/ChangeLog:
* gcc.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107998
--- Comment #4 from Christophe Lyon ---
Indeed my patch aimed at catching such inconsistencies.
I guess before that the build had a 'strange' behavior? (with a missing
dirname, some parts of the shell genmultilib shell script would expand into
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108003
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |13.0
Hi!
On 2022-12-07T07:04:10+0100, Sebastian Huber
wrote:
> On 06.12.22 22:06, Thomas Schwinge wrote:
> I suppose I just fail to see some detail here, but:
>
>> On 2022-11-21T08:25:25+0100, Sebastian
>> Huber wrote:
>>> gcc/ChangeLog:
>>>
>>>* gcc.cc (SUBTARGET_CC1_SPEC): Define if not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108000
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |erozen at microsoft dot
com
On Wed, Dec 7, 2022 at 7:36 AM Hongyu Wang wrote:
>
> For Alderlake there is similar issue like PR 81616, enable
> avoid_fma256_chain will also benefit on Intel latest platforms
> Alderlake and Sapphire Rapids.
>
> Bootstrapped/regtested on x86_64-pc-linux-gnu{-m32,}.
>
> Ok for master?
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108002
--- Comment #5 from Richard Biener ---
Btw, you can always try to bisect what GCC change fixed the issue and try
backporting this yourself.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108004
--- Comment #3 from HaoChen Gui ---
(In reply to Andrew Pinski from comment #2)
> Especially when it comes to signed comparisons.
>From the ISA,
For all fixed-point instructions in which Rc=1, and for
addic., andi., and andis., the first three
On Tue, Dec 06, 2022 at 05:36:54PM +0800, Kewen.Lin wrote:
> Hi Mike,
>
> Thanks for fixing this!
>
> Could you help to elaborate why we need to disable it during libgcc building?
When you are building libgcc, you are building the __mulkc3, __divkc3
functions. The mapping in the compiler
For Alderlake there is similar issue like PR 81616, enable
avoid_fma256_chain will also benefit on Intel latest platforms
Alderlake and Sapphire Rapids.
Bootstrapped/regtested on x86_64-pc-linux-gnu{-m32,}.
Ok for master?
gcc/ChangeLog:
* config/i386/x86-tune.def
I do see make using ‘GDC' while building gcc compiler, maybe try changing that ?
- Ankur
> On 07-Dec-2022, at 11:42 AM, Dave Blanchard wrote:
>
> Is there an environment variable like 'CC' or 'CXX', which specifies the name
> of the D compiler to use, which I might need to set when
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105523
Ahmad Fatoum changed:
What|Removed |Added
CC||ahmad at a3f dot at
--- Comment #14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108004
--- Comment #2 from Andrew Pinski ---
Especially when it comes to signed comparisons.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108004
--- Comment #1 from Andrew Pinski ---
>From what I remember and. Only sets eq bit correctly.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108004
Bug ID: 108004
Summary: x-form logical operations with dot instructions are
not emitted.
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Is there an environment variable like 'CC' or 'CXX', which specifies the name
of the D compiler to use, which I might need to set when bootstrapping GCC?
Thanks.
--
Dave Blanchard
On 06.12.22 22:06, Thomas Schwinge wrote:
Hi!
I suppose I just fail to see some detail here, but:
On 2022-11-21T08:25:25+0100, Sebastian
Huber wrote:
gcc/ChangeLog:
* gcc.cc (SUBTARGET_CC1_SPEC): Define if not defined.
(cc1_spec): Append SUBTARGET_CC1_SPEC.
---
v2: Append
on 2022/12/7 13:24, HAO CHEN GUI wrote:
> Hi Kewen,
> Thanks so much for your review comments. I will fix them.
>
> 在 2022/12/7 11:06, Kewen.Lin 写道:
>> Does this issue which relies on the fix for generic part make bootstrapping
>> fail?
>> If no, how many failures it can cause? I'm thinking
Hi Kewen,
Thanks so much for your review comments. I will fix them.
在 2022/12/7 11:06, Kewen.Lin 写道:
> Does this issue which relies on the fix for generic part make bootstrapping
> fail?
> If no, how many failures it can cause? I'm thinking if we can commit this
> firstly,
> then in the
Hi,
This patch adds a new conversion to convert a certain branch to
conditional ternary set in ifcvt.
The branch commonly has following insns.
cond_jump ? pc : label
setcc
(neg/subreg)
label: set a constant
cond_jump and setcc use the same CC reg and neg/subreg is optional.
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105095
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |11.4
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104822
--- Comment #3 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #2)
> Mine, I think this patch will fix the issue:
Which is similar to the check above dealing with named address spaces.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104822
Andrew Pinski changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105043
Andrew Pinski changed:
What|Removed |Added
Resolution|MOVED |---
Summary|Please document
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108002
--- Comment #4 from Grant Li ---
(In reply to Andrew Pinski from comment #3)
> # pragma GCC optimize("-O2")
>
> The bugs that related to this pragma were fixed in GCC 4.8.0 (a few were
> fixed before).
> There were many changes that helped
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108003
Bug ID: 108003
Summary: [13 Regression] ICE in bitmap_check_index, at
sbitmap.h:105
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108002
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108002
--- Comment #2 from Grant Li ---
(In reply to Andrew Pinski from comment #1)
> 4.4.3 is over 12 years old now. Is there any way to move to something newer?
I already tried gcc 4.4.7 and 4.4.4... but also had same error.
We need to compatible
Hi Haochen,
on 2022/12/6 13:44, HAO CHEN GUI wrote:
> Hi,
> This patch enables "have_cbranchcc4" on rs6000 by defining
> a "cbranchcc4" expander. "have_cbrnachcc4" is a flag in ifcvt.cc
> to indicate if branch by CC bits is invalid or not. With this
> flag enabled, some branches can be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108002
--- Comment #1 from Andrew Pinski ---
4.4.3 is over 12 years old now. Is there any way to move to something newer?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108002
Bug ID: 108002
Summary: Throwing exception when compiling third-parties(ZSTD)
libraries with optimization option
Product: gcc
Version: 4.4.3
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107992
--- Comment #1 from Ian Lance Taylor ---
Thanks. This is happening because the data structures that Go's garbage
collector uses require that all pointers be aligned on their natural
boundaries. Unfortunately m68k only provides 2-byte
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108001
Bug ID: 108001
Summary: unamed struct extension is documented for C++
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: documentation
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18474
--- Comment #2 from Andrew Pinski ---
Note this is only invalid as n (if declared correctly) was not depedent so the
operator lookup would be bound at definition time.
That is the following needs to be accepted still:
template
void g(void)
{
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106708
--- Comment #1 from Jiu Fu Guo ---
PR93178 also mentioned the "li,oris" case.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105059
Andrew Pinski changed:
What|Removed |Added
Keywords|accepts-invalid |documentation
Ever confirmed|0
Hi Nathan,
> 1) 'save' -- does it *cause* the bmi to be saved, or is that actually
> controlled
by other options? (I suspect the latter)
Yes, it causes the bmi to be saved. In fact, when we add `-save-temps` option
in clang and we compile a module unit, we'll see the preprocessed output, the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104975
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105049
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
Summary|ICE: in
Hi,
In the recent discussion on how to make some built-in type only valid for
some target features efficiently[1], Andrew mentioned this patch which he
made previously (Thanks!). I confirmed it can help rs6000 related issue,
and noticed PR99657 is still opened, so I think we still want this to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103302
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
--- Comment #18 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105047
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
On Wed, 7 Dec 2022, 00:36 Nathan Sidwell via Gcc, wrote:
> On 12/6/22 16:03, David Blaikie wrote:
> > Over in https://reviews.llvm.org/D137059 we're discussing the naming
> > of a clang flag - would be good to have it be consistent with GCC.
> >
> > The functionality is to name the BMI (.pcm in
gcc/ChangeLog:
* doc/rtl.texi: Correct a clerical error in the document.
---
gcc/doc/rtl.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/doc/rtl.texi b/gcc/doc/rtl.texi
index 43c9ee8bffe..44858d12892 100644
--- a/gcc/doc/rtl.texi
+++ b/gcc/doc/rtl.texi
@@
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107967
--- Comment #10 from caiyinyu ---
(In reply to Jakub Jelinek from comment #9)
> Created attachment 54029 [details]
> gcc13-pr107967.patch
>
> Untested fix. Deferring the mode_composite stuff for later.
There are still some fails and errors
I initially ran into this while reviving autoprofiledbootstrap build.
I was able to create a simple reliable test for this bug and captured it in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108000
I also included the test case in the updated patch below.
Eugene
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107970
Hongtao.liu changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107970
--- Comment #2 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:da7fb32d403759daefefc79dc251d2437c1b638c
commit r13-4532-gda7fb32d403759daefefc79dc251d2437c1b638c
Author: liuhongt
Date: Tue Dec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105050
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105050
--- Comment #7 from Andrew Pinski ---
I think clang still gives a better error message here though:
:43:15: error: static assertion expression is not an integral constant
expression
static_assert(test_swap());
^~~
:18:17:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108000
--- Comment #2 from Eugene Rozenfeld ---
I actually have a fix for this, just wanted to file a simple test case. I
initially ran into this failure while reviving autoprofiledbootstrap build. The
failure happens while using the profile and the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108000
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2022-12-07
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108000
--- Comment #1 from Andrew Pinski ---
Can you provide the exact command lines being used and does it fail during
while using the profile or before?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107980
--- Comment #12 from joseph at codesourcery dot com ---
The standard rule about not using extra arguments means that any warnings
would need to avoid even converting those arguments from pp-tokens to
tokens; it's OK for them to contain
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108000
Bug ID: 108000
Summary: Assert during ipa-cp with AutoFDO
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107999
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
Thanks Richard for your review and for pointing out the issue with BTI.
The current patch removes the existing BTI instruction,
and then adds the BTI hint when expanding the patchable_area pseudo.
The attached patch passed bootstrap and regression test on arm64-linux.
Ok to commit to gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107770
Antoni changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107954
--- Comment #3 from joseph at codesourcery dot com ---
Editorial review before the CD ballot slipped the schedule. Second-round
editorial review after a huge number of changes in the editorial review
slipped the schedule. Getting a final
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107999
Bug ID: 107999
Summary: test-error-array-bounds.c now fails because
[-Warray-bounds] was updated to [-Warray-bounds=] in
error messages
Product: gcc
Version:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107770
--- Comment #1 from CVS Commits ---
The master branch has been updated by Antoni Boucher :
https://gcc.gnu.org/g:d2e782cb99c3116c389d6a9565678c4ffe26
commit r13-4531-gd2e782cb99c3116c389d6a9565678c4ffe26
Author: Antoni Boucher
Date:
On 12/6/22 16:03, David Blaikie wrote:
Over in https://reviews.llvm.org/D137059 we're discussing the naming
of a clang flag - would be good to have it be consistent with GCC.
The functionality is to name the BMI (.pcm in Clang's parlance) output
file when compiling a C++20 module.
Current
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106611
--- Comment #6 from Nikolas Klauser ---
Is there any update on this?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107997
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-valid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107998
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
Component|bootstrap
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107998
--- Comment #2 from James McKelvey ---
Configured with:
./configure --enable-languages=c,c++ --enable-threads=posix
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107882
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107998
--- Comment #1 from James McKelvey ---
Created attachment 54032
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54032=edit
Config log
PR analyzer/107882 reports an ICE, due to trying to get a compound svalue
for this binding:
cluster for: a:
key: {bytes 0-3}
value: {UNKNOWN()}
key: {empty}
value: {UNKNOWN()}
key: {bytes 4-7}
value: {UNKNOWN()}
where there's an binding to the unknown value of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107882
--- Comment #4 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:dfe2ef7f2b6cac7017f32a0a04f74e1b6d9f1311
commit r13-4529-gdfe2ef7f2b6cac7017f32a0a04f74e1b6d9f1311
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107998
Bug ID: 107998
Summary: [13 Regression] gcc-13-20221204 failure to build on
Cygwin No dirname for option: m32
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107997
Bug ID: 107997
Summary: fd8dd6c03849691 probably uncovered an issue building
the Linux kernel
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106856
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
On Wed, 30 Nov 2022 at 18:00, François Dumont wrote:
>
> On 30/11/22 14:07, Jonathan Wakely wrote:
> > On Wed, 30 Nov 2022 at 11:57, Jonathan Wakely wrote:
> >>
> >>
> >> On Wed, 30 Nov 2022 at 11:54, Jonathan Wakely wrote:
> >>>
> >>>
> >>> On Wed, 30 Nov 2022 at 06:04, François Dumont via
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107871
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107979
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
Tested x86_64-linux. Pushed to trunk.
-- >8 --
This test was recently modified to check that the library doesn't use
__unused anywhere, because that's a macro in newlib. But it's also a
macro in old versions of glibc, so the test now fails for those targets.
Disable that check for those targets
Tested x86_64-linux. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
PR libstdc++/107871
* include/std/format (_Iter_sink::_M_overflow): Add cast to
size_t.
(_Iter_sink::_M_make_span): Use
typedef instead of decltype.
*
I've pushed this to trunk. Tested x86_64-linux.
On Mon, 21 Nov 2022 at 20:44, Jonathan Wakely via Libstdc++
wrote:
>
> While finishing the time zone support for C++20, I noticed that the
> chrono::hh_mm_ss type is surprisingly large: 40 bytes. That's because
> we use duration for each of the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107979
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:2a23b93f944fa78d4284eb5687051c224e5ab08f
commit r13-4528-g2a23b93f944fa78d4284eb5687051c224e5ab08f
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107871
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:9cce91a63dcc40cb39e68f6a771e891e51c51946
commit r13-4527-g9cce91a63dcc40cb39e68f6a771e891e51c51946
Author: Jonathan Wakely
Tested x86_64-linux. Pushed to trunk.
-- >8 --
The PR shows a bogus warning where jump threading generates code for the
undefined case that the insertion point is a value-initialized iterator
but _M_finish and _M_end_of_storage are unequal (so at least one must be
non-null). Using
Tested x86_64-linux. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* include/bits/std_mutex.h (mutex): Add nodiscard attribute to
try_lock member function.
* include/bits/unique_lock.h (unique_lock): Likewise for
try_lock, try_lock_until, try_lock_for member
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106434
--- Comment #11 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:4ba94abf147fe7778a7541849ce27cafee74df9b
commit r13-4525-g4ba94abf147fe7778a7541849ce27cafee74df9b
Author: Jonathan Wakely
Tested x86_64-linux. Pushed to trunk.
-- >8 --
Fix digit grouping for integers formatted with "{:#Lx}" which were
including the "0x" prefix in the grouped digits. This resulted in output
like "0,xff,fff" instead of "0xff,fff".
Also change std:::basic_format_parse_context to not throw for an
The 12/06/2022 11:58, Wilco Dijkstra wrote:
> > i don't think how[*RA_STATE] can ever be set to REG_SAVED_OFFSET,
> > this pseudo reg is not spilled to the stack, it is reset to 0 in
> > each frame and then toggled within a frame.
>
> It's is just a state, we can use any state we want since it is
Hi!
I suppose I just fail to see some detail here, but:
On 2022-11-21T08:25:25+0100, Sebastian Huber
wrote:
> gcc/ChangeLog:
>
> * gcc.cc (SUBTARGET_CC1_SPEC): Define if not defined.
> (cc1_spec): Append SUBTARGET_CC1_SPEC.
> ---
> v2: Append SUBTARGET_CC1_SPEC directly to cc1_spec
Over in https://reviews.llvm.org/D137059 we're discussing the naming
of a clang flag - would be good to have it be consistent with GCC.
The functionality is to name the BMI (.pcm in Clang's parlance) output
file when compiling a C++20 module.
Current proposal is to use
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107882
David Malcolm changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #3 from David
Sent from my iPhone
On Tue, 6 Dec 2022 at 20:32, Gavin Ray wrote:
>
> Ah got it, didn't know that (handy, will save me duplicating a bunch of
> attributes).
> Thanks Jonathan!
The Clang doc acually show all the forms that can be used for each attribute:
https://clang.llvm.org/docs/AttributeReference.html#may-alias
Ah got it, didn't know that (handy, will save me duplicating a bunch of
attributes).
Thanks Jonathan!
On Tue, Dec 6, 2022 at 2:23 PM Jonathan Wakely
wrote:
>
>
> On Tue, 6 Dec 2022, 18:36 Gavin Ray via Gcc, wrote:
>
>> Oh, D'oh! Thanks Joseph, apologies for the needless email on the list
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107967
--- Comment #9 from Jakub Jelinek ---
Created attachment 54029
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54029=edit
gcc13-pr107967.patch
Untested fix. Deferring the mode_composite stuff for later.
From: Björn Schäpers
This is actually needed so that libstdc++'s implementation
to be able to work on windows.
Tested on x86_64-linux and i686-w64-mingw32.
-- >8 --
* configure.ac: Add a check for windows.h.
* configure, config.h.in: Regenerate.
* fileline.c: Add
From: Björn Schäpers
Any underflow which might happen, will be countered by an overflow in
dwarf.c.
Tested on x86_64-linux and i686-w64-mingw32.
-- >8 --
Fixes https://github.com/ianlancetaylor/libbacktrace/issues/89 and
https://github.com/ianlancetaylor/libbacktrace/issues/82.
*
From: Björn Schäpers
Fixes https://github.com/ianlancetaylor/libbacktrace/issues/53, except
that libraries loaded after the backtrace_initialize are not handled.
But as far as I can see that's the same for elf.
Tested on x86_64-linux and i686-w64-mingw32.
-- >8 --
* pecoff.c
From: Björn Schäpers
It's the right thing to do, since the PC shouldn't go out of the
uintptr_t domain, and in backtrace_pcinfo the pc is uintptr_t.
This is a preparation for a following patch.
Tested on x86_64-linux and i686-w64-mingw32.
-- >8 --
* dwarf.c: changed variables holding
Version 4 contains two missed feedback suggestions (namespace in
m2pp.cc) and use build_nonstandard_integer_type in
gm2-lang.cc:gm2_type_for_size.
This patch set contains the .h, .cc and .flex files found in
gcc/m2. The files are tightly coupled with the gimple interface
(see
On Tue, 6 Dec 2022, 18:36 Gavin Ray via Gcc, wrote:
> Oh, D'oh! Thanks Joseph, apologies for the needless email on the list then.
>
> One final question if I could -- does that mean that in order to support
> "may-alias" with the bracket syntax on both Clang and GCC, it would
> require:
>
>
1 - 100 of 331 matches
Mail list logo
