On 2/28/25 02:56, Andre Vehreschild wrote:
Hi Sandra,
thanks for taking on the laborious task. I have browsed over the changes and
found:
Patch 3 in intrinsic.texi:
@@ -2071,6 +2071,9 @@ end program atomic
@cindex Atomic subroutine, ADD with fetch
@table @asis
+@item @emph{Synopsis}:
+@co
Dear all,
due to an oversight in the Fortran standard before 2018,
empty derived types with bind(C) attribute were explicitly
(deliberately?) accepted by gfortran, giving a warning that
the companion processor might not provide an interoperating
entity.
In the PR, Tobias pointed to a discussion
On 2025-01-13 17:48, Tobias Burnus wrote:
Andreas Schwab wrote:
This breaks m68k:
Same issue on GCN, hence I filed https://gcc.gnu.org/PR118418
This also breaks gcc bootstrap on riscv64 under some specific configuration:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119012#c12
Although it doe
Support for dynamic selectors in "declare variant" was developed in
parallel with support for the adjust_args/append_args clauses and the
dispatch construct; they collided in a bad way. This patch fixes the
"sorry" for calls that need both by removing the adjust_args/append_args
code from gimplify
They are the same.
gcc/ChangeLog:
* config/loongarch/sync.md (atomic_optab): Remove.
(atomic_): Change atomic_optab to amop.
(atomic_fetch_): Likewise.
---
gcc/config/loongarch/sync.md | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/gcc/config/lo
I'm not sure if I goof'd this or if I merely upstreamed someone else's
goof. Either way the long branch code isn't working correctly.
We were using 'n' as the output modifier to negate the condition. But
'n' has a special meaning elsewhere, so when presented with a condition
rather than what
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Swedish team of translators. The file is available at:
https://translationproject.org/latest/gcc/sv.po
(This file, 'gcc-15-b20250216.sv.po',
This patch adds a new section "AVR Optimization Options"
in the texi documentation.
Ok for trunk?
Johann
--
AVR: Add texi @subsubsection "AVR Optimization Options".
gcc/
* doc/invoke.texi (AVR Optimization Options): New @subsubsection
for pure optimization options.
diff --git
They could be incorrectly reordered with store instructions like st.b
because the RTL expression does not have a memory_operand or a (mem)
expression. The incorrect reorder has been observed in openh264 LTO
build.
Expand them to a (mem) expression instead of unspec to fix the issue.
Then we need
The patch for target/116256 significantly simplified the condition and,
I guess not too surprisingly, exposed a minor code quality regression.
Specifically the split part of the define_insn_and_split only splits
after reload (because we use a match_scratch). So there's nothing to
combine th
10 matches
Mail list logo