Re: [PATCH] fold: Optimise fold_view_convert_expr

On Sun, Dec 5, 2021 at 11:00 PM Richard Sandiford via Gcc-patches wrote: > > When compiling an optabs.ii at -O2 with a release-checking build, > there were 210,172 calls to fold_view_convert_expr. 99.8% of them > were conversions of an INTEGER_CST to an ENUMERAL_TYPE, so this patch > adds a

Re: [PATCH] alias: Optimise call_may_clobber_ref_p

On Sun, Dec 5, 2021 at 10:59 PM Richard Sandiford via Gcc-patches wrote: > > When compiling an optabs.ii at -O2 with a release-checking build, > we spent a lot of time in call_may_clobber_ref_p. One of the > first things the function tries is the get_modref_function_summary > approach, but that

[Bug libstdc++/51653] More compact std::tuple

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51653 --- Comment #6 from Marc Glisse --- (In reply to Andrew Pinski from comment #5) > Is there anything more to do for this? Yes. This PR is about having the library reorder the elements of a tuple to minimize the size, and the current code does

Re: [PATCH] ranger: Add shortcuts for single-successor blocks

On Sun, Dec 5, 2021 at 10:58 PM Richard Sandiford via Gcc-patches wrote: > > When compiling an optabs.ii at -O2 with a release-checking build, > there were 6,643,575 calls to gimple_outgoing_range_stmt_p. 96.8% of > them were for blocks with a single successor, which never have a control >

Re: [PATCH] ranger: Optimise irange_union

On Sun, Dec 5, 2021 at 10:55 PM Richard Sandiford via Gcc-patches wrote: > > When compiling an optabs.ii at -O2 with a release-checking build, > the hottest function in the profile was irange_union. This patch > tries to optimise it a bit. The specific changes are: > > - Use quick_push rather

Re: [PATCH 2/2] Use dominators to reduce ranger cache-flling.

On Fri, Dec 3, 2021 at 9:42 PM Andrew MacLeod via Gcc-patches wrote: > > When a request is made for the range of an ssa_name at some location, > the first thing we do is invoke range_of_stmt() to ensure we have looked > at the definition and have an evaluation for the name at a global > level. I

Re: [PATCH 1/2] - Add BB option for outgoing_edge_range_p.

On Fri, Dec 3, 2021 at 9:41 PM Andrew MacLeod via Gcc-patches wrote: > > has_edge_range_p() and may_recompute_p() currently only take an optional > edge as a parameter. They only indicate if a range *might* be > calculated for a name, but they do not do any calculations. > > To determine the

[Bug c++/86588] peculiar build issue using range-v3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86588 --- Comment #4 from Andrew Pinski --- The error message for "-std=gnu++17 -fconcepts" case: In file included from /home/mi/h4nn3s/devel/seqan3/include/seqan3/range/view/take_line.hpp:46, from test.cpp:1:

[Bug c++/86588] peculiar build issue using range-v3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86588 --- Comment #3 from Andrew Pinski --- On the trunk with "std=c++17 -fconcepts" It does not ICE any more but without it, GCC does.

[Bug libstdc++/100912] powerpc64le: ieee128 long double incorrectly printed when using shared libstdc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100912 --- Comment #9 from Qiu Chaofan --- I also get following 'symbol not found' error for following case (under -mabi=ieeelongdouble): undefined reference to `std::__gnu_cxx11_ieee128::money_get > >::money_get(unsigned long)' Maybe related?

Re: [PATCH 3/5] gcc: Add --nostdlib++ option

On Sun, Dec 5, 2021 at 6:43 AM Richard Purdie via Gcc-patches wrote: > > On Thu, 2021-12-02 at 20:04 -0700, Jeff Law wrote: > > > > On 10/28/2021 10:39 AM, Richard Purdie wrote: > > > On Thu, 2021-10-28 at 08:51 -0600, Jeff Law wrote: > > > > On 10/27/2021 2:05 PM, Richard Purdie via Gcc-patches

[Bug c++/83756] [9/10/11/12 Regression] gcc ICE in gimplify_expr on boost::call_once (-fms-extensions)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83756 Andrew Pinski changed: What|Removed |Added CC||sonoro at telefonica dot net ---

[Bug target/69832] internal compiler error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69832 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/13452] No error on invalid CV qualifier on member function returning function pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=13452 Andrew Pinski changed: What|Removed |Added CC||zhonghao at pku dot org.cn --- Comment

[Bug c++/86652] pointer to function type cannot have 'const' qualifier

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86652 Andrew Pinski changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/69898] Possibility for function with cv-qualifier-seq be adjusted to function pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69898 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug c++/13452] No error on invalid CV qualifier on member function returning function pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=13452 --- Comment #8 from Andrew Pinski --- http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#1417

[Bug rtl-optimization/69933] non-ideal branch layout for an early-out return

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69933 Andrew Pinski changed: What|Removed |Added Known to fail||8.1.0 Known to work|

[Bug preprocessor/67046] [9/10/11/12 Regression] Segmentation fault when a preprocessor directive follows the argument to _Pragma

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67046 Andrew Pinski changed: What|Removed |Added Known to work||4.1.2, 4.4.7 Ever confirmed|0

[Bug objc/66367] Objective-C Variadic Method Not Compiling

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66367 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

Re: [PATCH v8 2/2] Don't move cold code out of loop by checking bb count

On 2021/12/6 13:09, Xionghu Luo via Gcc-patches wrote: > > > On 2021/12/1 18:09, Richard Biener wrote: >> On Wed, Nov 10, 2021 at 4:08 AM Xionghu Luo wrote: >>> >>> >>> >>> On 2021/11/4 21:00, Richard Biener wrote: On Wed, Nov 3, 2021 at 2:29 PM Xionghu Luo wrote: > > >> +

[Bug target/66025] Implement ThreadSanitizer support for IBM z Systems

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66025 Andrew Pinski changed: What|Removed |Added Resolution|--- |FIXED Target Milestone|---

[Bug c++/65861] libstdc++ is silently generating wrong code when its std::search is given an input iterator

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65861 Andrew Pinski changed: What|Removed |Added Keywords||accepts-invalid Resolution|---

Ping: [PATCH v2] Fix incorrect loop exit edge probability [PR103270]

Hi Honza, Gentle ping for this :), thanks. https://gcc.gnu.org/pipermail/gcc-patches/2021-November/585289.html On 2021/11/24 13:03, Xionghu Luo via Gcc-patches wrote: > On 2021/11/23 17:50, Jan Hubicka wrote: >>> On Tue, Nov 23, 2021 at 6:52 AM Xionghu Luo wrote: r12-4526 cancelled

[Bug sanitizer/57507] gcc 4.8: thread sanitizer: std::thread false(?) positive

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57507 Andrew Pinski changed: What|Removed |Added CC||p.bartosiewi at partner dot samsun

[Bug sanitizer/64337] ThreadSanitizer: std::thread + lambda false positive

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64337 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug sanitizer/57507] gcc 4.8: thread sanitizer: std::thread false(?) positive

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57507 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

Re: [PATCH v8 2/2] Don't move cold code out of loop by checking bb count

On 2021/12/1 18:09, Richard Biener wrote: > On Wed, Nov 10, 2021 at 4:08 AM Xionghu Luo wrote: >> >> >> >> On 2021/11/4 21:00, Richard Biener wrote: >>> On Wed, Nov 3, 2021 at 2:29 PM Xionghu Luo wrote: > + while (outmost_loop != loop) > +{ > + if

[Bug libstdc++/51653] More compact std::tuple

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51653 --- Comment #5 from Andrew Pinski --- Is there anything more to do for this?

[Bug debug/58767] assemly output (labels order) depends on the sources location.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58767 --- Comment #1 from Andrew Pinski --- The output of the strings is based on the the traverse of the hashtable. this might mean the output of the strings in the hashtable be outputted at a different location based on the hash of the strings. In

[Bug c++/103569] New: Type alias from result of lambda call in unevaluated context, used in template, is inconsistent

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103569 Bug ID: 103569 Summary: Type alias from result of lambda call in unevaluated context, used in template, is inconsistent Product: gcc Version: 11.1.0 Status: UNCONFIRMED

Re: [PATCH] [i386] Prefer INT_SSE_REGS for SSE_FLOAT_MODE_P in preferred_reload_class.

Forget --in-reply-to when git send-email. > I was thinking about: > > --cut here-- > @@ -19194,9 +19194,17 @@ ix86_preferred_reload_class (rtx x, > reg_class_t regclass) > return NO_REGS; > } > > - /* Prefer SSE regs only, if we can use them for math. */ > + /* Prefer SSE if we can

[PATCH] [i386] Prefer INT_SSE_REGS for SSE_FLOAT_MODE_P in preferred_reload_class.

When moves between integer and sse registers are cheap. 2021-12-06 Hongtao Liu Uroš Bizjak gcc/ChangeLog: PR target/95740 * config/i386/i386.c (ix86_preferred_reload_class): Allow integer regs when moves between register units are cheap. *

Re: [PATCH] [PATCH,v2,1/1,AARCH64][PR102768] aarch64: Add compiler support for Shadow Call Stack

On 12/6/21 10:41 AM, Dan Li wrote: Shadow Call Stack can be used to protect the return address of a function at runtime, and clang already supports this feature[1]. To enable SCS in user mode, in addition to compiler, other support is also required (as discussed in [2]). This patch only adds

Re: [PATCH] gcc: vxworks: fix providing stdint.h header

On Dec 3, 2021, Olivier Hainque wrote: > Alex, how does that look to you? LGTM, thanks, -- Alexandre Oliva, happy hackerhttps://FSFLA.org/blogs/lxo/ Free Software Activist GNU Toolchain Engineer Disinformation flourishes because many people care

[Bug target/102768] [feature request] Add compiler support for aarch64 shadow call stack

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102768 --- Comment #7 from ashimida --- Hi nsz, Could you please review this patch :) Link: https://gcc.gnu.org/pipermail/gcc-patches/2021-December/586204.html Thanks, -- Dan

[PATCH] [PATCH, v2, 1/1, AARCH64][PR102768] aarch64: Add compiler support for Shadow Call Stack

Shadow Call Stack can be used to protect the return address of a function at runtime, and clang already supports this feature[1]. To enable SCS in user mode, in addition to compiler, other support is also required (as discussed in [2]). This patch only adds basic support for SCS from the compiler

[Bug libfortran/103560] Error: GFC_INTEGER_4 should be available for the library to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103560 --- Comment #1 from brocolis at eml dot cc --- Actually the first error message is make[2]: Entering directory '/build/mingw/build-gcc-git/x86_64-w64-mingw32/libgfortran' /bin/sh ../../../gcc-git/libgfortran/mk-kinds-h.sh '1 2 4 8 16' '4 8 10

[Bug target/103568] New: sub-optimal vector construction with two loaded doubles on Power10

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103568 Bug ID: 103568 Summary: sub-optimal vector construction with two loaded doubles on Power10 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal

gcc-12-20211205 is now available

Snapshot gcc-12-20211205 is now available on https://gcc.gnu.org/pub/gcc/snapshots/12-20211205/ 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

[Bug middle-end/103364] s390x: TLS reference in /usr/lib64/libLLVM.so mismatches non-TLS reference in /usr/lib64/libLLVM.so

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103364 --- Comment #18 from Sarah Julia Kriesch --- (In reply to Andreas Krebbel from comment #17) > (In reply to Sarah Julia Kriesch from comment #12) > > that is happening during the build process in OBS with a really minimal > > openSUSE

[PATCH] gimple: Optimise inlined gimple_seq_last

In self-compilations, GCC doesn't realise that gimple_seq_last always returns nonnull when the argument is nonnull. Although it's a small thing in itself, the function is used (indirectly) many times and the extra null checks bloat what are otherwise simple loops. This patch adds an optimisation

[PATCH] fold: Optimise fold_view_convert_expr

When compiling an optabs.ii at -O2 with a release-checking build, there were 210,172 calls to fold_view_convert_expr. 99.8% of them were conversions of an INTEGER_CST to an ENUMERAL_TYPE, so this patch adds a fast(er) path for that case. Tested on aarch64-linux-gnu and x86_64-linux-gnu. OK to

[PATCH] alias: Optimise call_may_clobber_ref_p

When compiling an optabs.ii at -O2 with a release-checking build, we spent a lot of time in call_may_clobber_ref_p. One of the first things the function tries is the get_modref_function_summary approach, but that also seems to be the most expensive check. At least for the optabs.ii test, most of

[PATCH] ranger: Add shortcuts for single-successor blocks

When compiling an optabs.ii at -O2 with a release-checking build, there were 6,643,575 calls to gimple_outgoing_range_stmt_p. 96.8% of them were for blocks with a single successor, which never have a control statement that generates new range info. This patch therefore adds a shortcut for that

[Bug fortran/103418] random_number() does not accept pointer, intent(in) array argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103418 anlauf at gcc dot gnu.org changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot

[PATCH] PR fortran/103418 - random_number() does not accept pointer, intent(in) array argument

Dear all, the check of dummy arguments with pointer attribute and INTENT(IN) was broken in the case the argument was passed to an intrinsic. We therefore rejected valid code as e.g. given in the PR. The patch relaxes the excessive check. This requires the adjustment of one of the tests for

[PATCH] ranger: Optimise irange_union

When compiling an optabs.ii at -O2 with a release-checking build, the hottest function in the profile was irange_union. This patch tries to optimise it a bit. The specific changes are: - Use quick_push rather than safe_push, since the final number of entries is known in advance. - Avoid

[Bug pch/71934] pch cannot be disabled so gcc cannot be position independent

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71934 Jakub Jelinek changed: What|Removed |Added Attachment #51926|0 |1 is obsolete|

[pushed] Objective-C, NeXT: Reorganise meta-data declarations.

This moves the GTY declaration of the meta-data indentifier array into the header that enumerates these and provides shorthand defines for them. This avoids a problem seen with a relocatable PCH implementation. Tested on x86_64, i686 Darwin, pushed to master, thanks Iain Signed-off-by: Iain

[Bug fortran/103567] Compile error with assumed-rank RESULT variable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103567 anlauf at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug fortran/103567] Compile error with assumed-rank RESULT variable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103567 --- Comment #1 from Wileam Yonatan Phan --- Surprisingly, this one compiles just fine: subroutine f(y) real, intent(out) :: y(..) end subroutine f

[Bug fortran/103567] New: Compile error with assumed-rank RESULT variable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103567 Bug ID: 103567 Summary: Compile error with assumed-rank RESULT variable Product: gcc Version: 10.3.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c++/103566] New: confusing error message for typedefs with initializers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103566 Bug ID: 103566 Summary: confusing error message for typedefs with initializers Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c++/103540] diagnosting concept depends on itself

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103540 --- Comment #2 from Igel --- Ah thanks for copying the relevant code here. The error that you're referring to is: : In instantiation of 'struct X<0>': :5:14: required by substitution of 'template requires StrictNodeType using Int = int

[Bug tree-optimization/103565] GCC emits more assembly than clang for carry flag

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103565 --- Comment #1 from cqwrteur --- https://godbolt.org/z/bGfY6zh9x #include template inline constexpr bool add_carry_pattern(bool carry,T a,T b,T& out) noexcept { T temp{carry+a}; out=temp+b; return (out < b) | (temp <

[Bug tree-optimization/103565] New: GCC emits more assembly than clang for carry flag

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103565 Bug ID: 103565 Summary: GCC emits more assembly than clang for carry flag Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug pch/71934] pch cannot be disabled so gcc cannot be position independent

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71934 --- Comment #22 from Jakub Jelinek --- That is true, but for the common case the relocation table sits in between two parts that need to be used, so in the common case it fseeks over it. I was hoping the relocation table could be last, but that

[Bug c++/103564] New: type-requirement that names a constructor should fail

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103564 Bug ID: 103564 Summary: type-requirement that names a constructor should fail Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: accepts-invalid Severity: normal

[Bug pch/71934] pch cannot be disabled so gcc cannot be position independent

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71934 --- Comment #21 from Iain Sandoe --- I'm not sure that the file size is that critical. IIUC, we never even read the relocation table unless the target returns a different mapped address from the one in the file, and we hope to choose VMA

[Bug pch/71934] pch cannot be disabled so gcc cannot be position independent

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71934 --- Comment #20 from Jakub Jelinek --- Thanks, you've got far further than I ended up with. I'll incorporate your changes tomorrow. And indeed, the PIE relocation code needs to take the bias into account and I even noted I need to do that, but

Portable solutions for carry flags?

Thank you!!! Sent from Mail for Windows

[Bug pch/71934] pch cannot be disabled so gcc cannot be position independent

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71934 --- Comment #19 from Iain Sandoe --- (In reply to Iain Sandoe from comment #18) > I needed two small additions to build (c-family+Ada+fortran+lto) > 3. I have one failing ObjC test... > > (possibly a missing or incorrectly specified GTY(()) -

[Bug pch/71934] pch cannot be disabled so gcc cannot be position independent

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71934 --- Comment #18 from Iain Sandoe --- I needed two small additions to build (c-family+Ada+fortran+lto) ** Go and D not tested. diff --git a/gcc/ada/gcc-interface/decl.c b/gcc/ada/gcc-interface/decl.c index 93b6eb5bb45..af6b6bd14d4 100644 ---

Re: [PATCH 3/5] gcc: Add --nostdlib++ option

On Thu, 2021-12-02 at 20:04 -0700, Jeff Law wrote: > > On 10/28/2021 10:39 AM, Richard Purdie wrote: > > On Thu, 2021-10-28 at 08:51 -0600, Jeff Law wrote: > > > On 10/27/2021 2:05 PM, Richard Purdie via Gcc-patches wrote: > > > > OpenEmbedded/Yocto Project builds libgcc and the other gcc runtime

[Bug tree-optimization/103559] Can't optimize away < 0 check on sqrt

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103559 Ivan Sorokin changed: What|Removed |Added CC||vanyacpp at gmail dot com --- Comment

[Bug c++/103563] ostream operator<< resolved to variant containing type resulting in stack overflow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103563 --- Comment #2 from Andrew Pinski --- The following code is same example but removed the headers and such: namespace t { class g{}cout; template struct v { template v(T1&&){} }; class monostate {}; g <<(g , const char

Re: [power-ieee128] What should the math functions be annotated with?

On 05.12.21 01:35, Peter Bergner wrote: Instead of setting LD_LIBRARY_PATH=/home/tkoenig/lib64 could you try setting it to LD_LIBRARY_PATH='$ORIGIN/lib64' instead? This would allow the other system binaries to not find your /home/tkoenig/lib64 directory so they'd behave normally. However,

[Bug c++/103563] ostream operator<< resolved to variant containing type resulting in stack overflow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103563 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/103563] New: ostream operator<< resolved to variant containing type resulting in stack overflow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103563 Bug ID: 103563 Summary: ostream operator<< resolved to variant containing type resulting in stack overflow Product: gcc Version: 11.1.0 Status: UNCONFIRMED

[Bug tree-optimization/56631] duplicated sse code in switch

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56631 Andrew Pinski changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[Bug c/61469] language feature: Support for enum underlying type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61469 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug libstdc++/56861] std::vector::reserve optimization bug

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56861 Andrew Pinski changed: What|Removed |Added Resolution|--- |WORKSFORME

[Bug sanitizer/55441] ThreadSanitizer: handle bitfields

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55441 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Target Milestone|---

[Bug middle-end/60937] -Os -fprofile-arcs breaks __attribute__((error()))

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60937 Andrew Pinski changed: What|Removed |Added Keywords||missed-optimization --- Comment #1 from

[Bug tree-optimization/48316] missed CSE / reassoc with array offsets

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48316 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2021-12-05

[Bug target/59842] `__x86.get_pc_thunk.bx' referenced in section `.text': defined in discarded section…

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59842 Andrew Pinski changed: What|Removed |Added See Also||https://sourceware.org/bugz

[Bug target/59842] `__x86.get_pc_thunk.bx' referenced in section `.text': defined in discarded section…

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59842 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug plugins/58445] dragonegg needs plugin/include/config/i386/stringop.def and plugin/include/config/i386/x86-tune.def installed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58445 Andrew Pinski changed: What|Removed |Added Resolution|--- |FIXED Target Milestone|---