https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112276
--- Comment #5 from Zdenek Sojka ---
(In reply to Hongtao.liu from comment #4)
> -(define_split
> - [(set (match_operand:V2HI 0 "register_operand")
> -(eq:V2HI
> - (eq:V2HI
> -(us_minus:V2HI
> -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112276
--- Comment #4 from Hongtao.liu ---
-(define_split
- [(set (match_operand:V2HI 0 "register_operand")
-(eq:V2HI
- (eq:V2HI
-(us_minus:V2HI
- (match_operand:V2HI 1 "register_operand")
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106627
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112282
Sam James changed:
What|Removed |Added
Summary|[14 Regression] wrong code |[14 Regression] wrong code
RV64 compare and branch instructions only support 64-bit operands.
At Expand time, the backend conservatively zero/sign extends
its operands even if not needed, such as incoming 32-bit function args
which ABI/ISA guarantee to be sign-extended already.
And subsequently REE fails to eliminate them
On 10/29/23 19:04, Vineet Gupta wrote:
RV64 compare and branch instructions only support 64-bit operands.
At Expand time, the backend conservatively zero/sign extends
its operands even if not needed, such as incoming 32-bit function args
which ABI/ISA guarantee to be sign-extended already.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104610
--- Comment #23 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:8c40b72036c967fbb1d1150515cf70aec382f0a2
commit r14-5002-g8c40b72036c967fbb1d1150515cf70aec382f0a2
Author: liuhongt
Date: Mon
Committed as r14-5001.
Thanks
Gui Haochen
在 2023/10/27 17:29, Richard Sandiford 写道:
> HAO CHEN GUI writes:
>> Hi,
>> This patch checks available optabs for scalar modes used in by
>> pieces operations. It fixes the regression cases caused by previous
>> patch. Now both scalar and vector modes
On 10/28/23 10:47, Roger Sayle wrote:
This patch optimizes PR middle-end/101955 for the ARC backend. On ARC
CPUs with a barrel shifter, using two shifts is (probably) optimal as:
asl_s r0,r0,31
asr_s r0,r0,31
but without a barrel shifter, GCC -O2 -mcpu=em currently
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111449
--- Comment #2 from CVS Commits ---
The master branch has been updated by HaoChen Gui :
https://gcc.gnu.org/g:8111b5c23bd14f80607bd35af58ec31e38a0378e
commit r14-5001-g8111b5c23bd14f80607bd35af58ec31e38a0378e
Author: Haochen Gui
Date: Mon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112276
Hongtao.liu changed:
What|Removed |Added
CC||crazylht at gmail dot com
--- Comment #3
RV64 compare and branch instructions only support 64-bit operands.
At Expand time, the backend conservatively zero/sign extends
its operands even if not needed, such as incoming 32-bit function args
which ABI/ISA guarantee to be sign-extended already.
And subsequently REE fails to eliminate them
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112282
--- Comment #6 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #5)
> But doing intializing au allows it work. that is:
> struct b au = {};
But I put a `__builtin_trap();` any place where au might be used as
uninitalized, and we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112282
--- Comment #5 from Andrew Pinski ---
Hmm it is not ah:
struct b ah = {};
still causes the infinite loop.
But doing intializing au allows it work. that is:
struct b au = {};
> From: Thomas Schwinge
> Date: Thu, 19 Oct 2023 12:42:26 +0200
> It's just GCC and Binutils/GDB, or are the top-level files also shared
> with additional projects?
Not sure if that counts as "shared", but I regularly drop
in* newlib to build simulator targets (*-elf, *-newabi).
That's
> From: Thomas Schwinge
> Date: Thu, 19 Oct 2023 12:42:26 +0200
> It's just GCC and Binutils/GDB, or are the top-level files also shared
> with additional projects?
Not sure if that counts as "shared", but I regularly drop
in* newlib to build simulator targets (*-elf, *-newabi).
That's
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112282
--- Comment #4 from Sam James ---
(In reply to Sam James from comment #3)
> I can't reproduce with 20231022, so I'll wait until today's snapshot
> finishes. That gives us a nice narrow window anyway...
Sorry, I was wrong there.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112282
--- Comment #3 from Sam James ---
I can't reproduce with 20231022, so I'll wait until today's snapshot finishes.
That gives us a nice narrow window anyway...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112282
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #2
On 10/26/23 13:37, Neal Frager wrote:
The MICROBLAZE_VERSION_COMPARE was incorrectly using strcasecmp
instead of strverscmp to check the mcpu version against feature
options. By simply changing the define to use strverscmp,
the new version 10.0 is treated correctly as a higher version
than
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112282
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-10-29
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112113
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112282
Andrew Pinski changed:
What|Removed |Added
Summary|wrong code (generated code |[14 Regression] wrong code
with: ../gcc-trunk/configure --disable-bootstrap
--enable-checking=yes --prefix=/local/suz-local/software/local/gcc-trunk
--enable-sanitizers --enable-languages=c,c++ --disable-werror --enable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 14.0.0 20231029 (experimental
Snapshot gcc-14-20231029 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20231029/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On 10/20/23 03:53, Christoph Muellner wrote:
From: Christoph Müllner
The XTheadFMemIdx ISA extension provides additional load and store
instructions for floating-point registers with new addressing modes.
The following memory accesses types are supported:
* load/store: [w,d]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112279
--- Comment #4 from Sam James ---
Minimised.
```
$ s390-ibm-linux-gnu-gcc -c sqlite-shell.i -O3 -march=arch13 -mzarch -c
sqlite-shell.i
sqlite-shell.i: In function 'shellAddSchemaName':
sqlite-shell.i:7:1: error: unrecognizable insn:
7 | }
On 10/20/23 03:53, Christoph Muellner wrote:
From: Christoph Müllner
The XTheadMemIdx ISA extension provides a additional load and store
instructions with new addressing modes.
The following memory accesses types are supported:
* load: b,bu,h,hu,w,wu,d
* store: b,h,w,d
The following
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112279
--- Comment #3 from Sam James ---
I can hit this with both a 13 cross compiler and 14 native.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112280
--- Comment #3 from Sam James ---
(In reply to Sam James from comment #2)
> I can't hit this with a 13 cross compiler.
(-> 14 regression)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112280
Sam James changed:
What|Removed |Added
Summary|ICE building|[14 regression] ICE
libstdc++: [_GLIBCXX_INLINE_VERSION] Add emul TLS symbols
libstdc++-v3/ChangeLog:
* config/abi/pre/gnu-versioned-namespace.ver: Add missing emul TLS
symbols.
François
diff --git a/libstdc++-v3/config/abi/pre/gnu-versioned-namespace.ver
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112281
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112281
--- Comment #1 from Andrew Pinski ---
-fno-tree-loop-distribution fixes the issue.
Looks like loop distribution is pulling out the assignment of `b = d[c + 1];`
from the loop even though the loop does assignment to a field of that `d[c +
1].a
This fixes handle_contract_violation under versioned namespace mode.
Tested under Linux x64 and confirmed to also fix Darwin build.
libstdc++: [_GLIBCXX_INLINE_VERSION] Provide handle_contract_violation
symbol
libstdc++-v3/ChangeLog:
* src/experimental/contract.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112281
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.4
Summary|wrong code at
-checking=yes --prefix=/local/suz-local/software/local/gcc-trunk
--enable-sanitizers --enable-languages=c,c++ --disable-werror --enable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 14.0.0 20231029 (experimental) (GCC)
[574] %
[574] % gcctk -O2 small.c; ./a.out
[575
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112280
--- Comment #1 from Sam James ---
s390-ibm-linux-gnu-gcc -c rijndael.i -O3 -march=arch13 -mzarch is enough to
reproduce (getting rid of -march=native)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112280
Bug ID: 112280
Summary: ICE building libgcrypt-1.10.2 on s390 (during GIMPLE
pass: ccp)
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112279
--- Comment #2 from Sam James ---
getting rid of -march=native: s390-ibm-linux-gnu-gcc -c sqlite3-shell.i -O3
-march=arch13 -mzarch ICEs for me
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112279
--- Comment #1 from Sam James ---
```
# gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/s390-ibm-linux-gnu/14/lto-wrapper
Target: s390-ibm-linux-gnu
Configured with:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112279
Bug ID: 112279
Summary: ICE building sqlite-3.43.2 on s390 (internal compiler
error: in extract_insn)
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112276
Thomas Koenig changed:
What|Removed |Added
CC||liuhongt at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112267
--- Comment #4 from Fabio Alemagna ---
With a tweak(In reply to Andrew Pinski from comment #3)
> (In reply to Fabio Alemagna from comment #1)
> > Changing the return type of the function func() from int to auto makes the
> > warning disappear.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110712
ibuclaw at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
Hi,
This patch fixes an ICE cause by the way the D front-end generates its
codegen around va_list types.
Static arrays in D are passed around by value, rather than decaying to a
pointer. On x86_64 __builtin_va_list is an exception to this rule, but
semantically it's still treated as a static
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110712
--- Comment #6 from CVS Commits ---
The releases/gcc-12 branch has been updated by Iain Buclaw
:
https://gcc.gnu.org/g:77f7d469e923f2bb1d21d3875290ce738262d42b
commit r12-9951-g77f7d469e923f2bb1d21d3875290ce738262d42b
Author: Iain Buclaw
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110712
--- Comment #5 from CVS Commits ---
The releases/gcc-13 branch has been updated by Iain Buclaw
:
https://gcc.gnu.org/g:46024d05a2cbbc1c2397e5728a98f90449b20ca4
commit r13-7992-g46024d05a2cbbc1c2397e5728a98f90449b20ca4
Author: Iain Buclaw
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110712
--- Comment #4 from CVS Commits ---
The master branch has been updated by Iain Buclaw :
https://gcc.gnu.org/g:ea8ffdcadb388b531adf4772287e7987a82a84b7
commit r14-4997-gea8ffdcadb388b531adf4772287e7987a82a84b7
Author: Iain Buclaw
Date: Sun
Hi Paul,
code->expr1->symtree->n.sym->ts = code->expr2->ts;
+ /* Sometimes the selector expression is given the typespec of the
+'_data' field, which is logical enough but inappropraite here. */
s/inappropraite/inappropriate/
+ if (code->expr2->ts.type
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110551
--- Comment #6 from Moncef Mechri ---
I confirm the extra mov disappears thanks to Roger's patch.
However, the codegen still seems suboptimal to me when using -march=haswell or
newer, even with Roger's patch:
uint64_t mulx64(uint64_t x)
{
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112278
Richard Sandiford changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112278
Bug ID: 112278
Summary: lra: ICE in partial_subreg_p for mixture of AdvSIMD &
SVE register asms
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112267
--- Comment #3 from Andrew Pinski ---
(In reply to Fabio Alemagna from comment #1)
> Changing the return type of the function func() from int to auto makes the
> warning disappear.
>
> Incidentally it causes an error on clang, though, which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112267
--- Comment #2 from Fabio Alemagna ---
Sorry, "from int to auto" should have been "from bool to auto". You get the
point.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112267
--- Comment #1 from Fabio Alemagna ---
Changing the return type of the function func() from int to auto makes the
warning disappear.
Incidentally it causes an error on clang, though, which prompts the question:
is this a clang bug, for
This moves a few simple patterns that are done in value replacement
in phiopt over to match.pd. Just the simple ones which might show up
in other code.
This allows some optimizations to happen even without depending
on sinking from happening and in some cases where phiopt is not
invoked (cond-1.c
This moves a few more value_replacements simplifications to match.
/* a == 1 ? b : a * b -> a * b */
/* a == 1 ? b : b / a -> b / a */
/* a == -1 ? b : a & b -> a & b */
Also adds a testcase to show can we catch these where value_replacement would
not
(but other passes would).
Bootstrapped and
This moves the value_replacement support for jump_function_from_stmt
to match pattern.
This allows us to optimize things earlier in phiopt1 rather than waiting
to phiopt2. Which means phiopt1 needs to be disable for vrp03.c testcase.
Bootstrapped and tested on x86_64-linux-gnu.
gcc/ChangeLog:
This set of 3 patches, copy what is being done in value replacement and
puts it into match-and-simplify form. I will be rewriting value_replacement
in phiopt to use match and simplify directly in the next few months but
I thought getting these into match form earlier on can help improve code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112269
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-10-29
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112272
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112277
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112273
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-10-29
Summary|gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19538
Eric Gallager changed:
What|Removed |Added
Keywords||diagnostic
--- Comment #5 from Eric
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112276
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-10-29
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112276
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82111
John David Anglin changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112275
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106627
Andrew Pinski changed:
What|Removed |Added
CC||erosenberger at kinetica dot
com
---
Hi,
This patch merges the D front-end and runtime library with upstream dmd
e48bc0987d, and standard library with phobos 2458e8f82.
Synchronizing with the v2.106.0-beta.1 release.
D front-end changes:
- Import dmd v2.106.0-beta.1.
D runtime changes:
- Import druntime v2.106.0-beta.1.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112277
Bug ID: 112277
Summary: Missed optimization of loop deletion because of missed
loopUnswitch and useless instruction elimination
Product: gcc
Version: 14.0
Status:
r14-4995-20231029071248-gc6929b08558-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20231029 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112275
Bug ID: 112275
Summary: target_clones breaks exception handling
Product: gcc
Version: 11.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112274
Bug ID: 112274
Summary: Bug due to unused expressions on s390x
Product: gcc
Version: 11.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Dimitry Andric writes:
> Ping. It would be nice to get this QoL fix in.
>
Yes please - we've been using this in Gentoo since around when it was
first posted. No complaints.
I cannot approve but it looks good to me.
> -Dimitry
>
>> On 28 Sep 2023, at 18:37, Dimitry Andric wrote:
>>
>> Ref:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94758
Sam James changed:
What|Removed |Added
Last reconfirmed||2023-10-29
Status|UNCONFIRMED
Bizarrely, since the fix for pr101625, the testcase compiles and runs
correctly with s/select type (y => x)/select type (y => (x))/ !
The fix is straightforward and appears to be one of those wrinkles arising
from the use of associate variables as a selector. The fault is reasonable
since the
On 2023-10-28 16:29, Martin Uecker wrote:
Isn't this testcase h() in builtin-dynamic-object-size-20.c? If you're
referring to testcase i(), then maybe "where the size is given by a
non-trivial function of a function parameter, e.g.
fn (size_t n, char buf[dummy(n)])."
h() is supported. For
Should be fixed by the below PATCH, feel free to ping me if any issues.
https://gcc.gnu.org/pipermail/gcc-patches/2023-October/634616.html
Pan
-Original Message-
From: Andreas Schwab
Sent: Saturday, October 28, 2023 4:16 PM
To: 钟居哲
Cc: patrick ; gcc-patches ;
kito.cheng ; rdapp.gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112273
Bug ID: 112273
Summary: gcc crashs when checking satisfaction a constraint of
lambda function
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
This change affects only Ada.
In gcc/ada/adaint.c(__gnat_get_file_names_case_sensitive), the
assumption for __APPLE__ is that file names are case-insensitive
unless __arm__ or __arm64__ are defined, in which case file names
are declared case-sensitive.
The associated comment is
"By default, we
On 28/10/23 3:56 pm, Ajit Agarwal wrote:
>
>
> On 28/10/23 4:09 am, Vineet Gupta wrote:
>>
>>
>> On 10/27/23 10:16, Bernhard Reutner-Fischer wrote:
>>> On Wed, 25 Oct 2023 16:41:07 +0530
>>> Ajit Agarwal wrote:
>>>
On 25/10/23 2:19 am, Vineet Gupta wrote:
> On 10/24/23 13:36,
On 28/10/23 3:55 pm, Ajit Agarwal wrote:
>
>
> On 27/10/23 10:46 pm, Bernhard Reutner-Fischer wrote:
>> On Wed, 25 Oct 2023 16:41:07 +0530
>> Ajit Agarwal wrote:
>>
>>> On 25/10/23 2:19 am, Vineet Gupta wrote:
On 10/24/23 13:36, rep.dot@gmail.com wrote:
> As said, I don't
Hello Vineet, Jeff and Bernhard:
This version 15 of the patch uses abi interfaces to remove zero and sign
extension elimination.
Bootstrapped and regtested on powerpc-linux-gnu.
In this version (version 15) of the patch following review comments are
incorporated.
a) Removal of hard code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112269
Andreas Schwab changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
--- Comment
This patch overhauls the ARC backend's insn_cost target hook, and makes
some related improvements to rtx_costs, BRANCH_COST, etc. The primary
goal is to allow the backend to indicate that shifts and rotates are
slow (discouraged) when the CPU doesn't have a barrel shifter. I should
also
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112112
Thomas Koenig changed:
What|Removed |Added
CC||tkoenig at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112269
Andreas Schwab changed:
What|Removed |Added
Target|x86_64 i?86 |x86_64 i?86 m68k-*-*
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112272
Bug ID: 112272
Summary: suboptimal zero-initialization of struct of mixed
pointer and integer types
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109334
Sam James changed:
What|Removed |Added
Ever confirmed|0 |1
Target Milestone|---
Tested on x86_64-darwin and x86_64-linux,
OK for trunk?
thanks
Iain
--- 8< ---
Earlier assembler support for complex fp16 on x86_64 Darin is broken. This
adds an additional test to the existing target-supports that fails for the
broken assemblers but works for the newer, fixed, ones.
Tested on x86_64-darwin, pushed to trunk, thanks
Iain
--- 8< ---
The large model is not implemented so far for Darwin (and the
codegen will be different when it is).
gcc/testsuite/ChangeLog:
* gcc.target/i386/large-data.c: Skip for Darwin.
Signed-off-by: Iain Sandoe
---
Tested on x86_64-darwin, pushed to trunk, thanks
Iain
--- 8< ---
Darwin platforms do not currently emit .cfi_xxx instructions so that these
tests do not work there.
gcc/testsuite/ChangeLog:
* gcc.target/i386/apx-interrupt-1.c: Skip for Darwin.
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109334
--- Comment #3 from CVS Commits ---
The master branch has been updated by Martin Uecker :
https://gcc.gnu.org/g:d96757842a13cad3500b74a352ab34d27a8be622
commit r14-4993-gd96757842a13cad3500b74a352ab34d27a8be622
Author: Martin Uecker
Date:
95 matches
Mail list logo
