nd it will be mashed into the rest of the kernels loop annotation
code for review before submission for mainline.
-Sandra
commit 1c9af55d7ff76e2e6b633af33e6e6991a0ba4c48
Author: Sandra Loosemore
Date: Sat Aug 22 18:23:26 2020 -0700
Permit calls to builtins and intrinsics in kernels
I've committed this relatively trivial patch to fix up some of the
kernels loop annotation tests on the OG10 branch to match changes in the
dump formatting.
-Sandra
commit 6d670e648e76fe44589a42ee458098ff84d24af1
Author: Sandra Loosemore
Date: Sat Aug 22 22:43:57 2020 -0700
Ping! Only the fix for the Fortran bootstrap failure in part 3 has been
reviewed.
-Sandra
https://gcc.gnu.org/pipermail/gcc-patches/2020-August/551927.html
On 8/13/20 10:34 AM, Sandra Loosemore wrote:
This is a revised version of the patch set originally posted
last November:
https
tches the variable appearing in the initializer. Much of the patch
is code refactoring, moving the initializer analysis out of
annotate_for_loop to check_and_annotate_for_loop so it can be
performed earlier.
2020-08-30 Sandra Loosemore
gcc/c-family/
* c-omp.c (annotate_for
r at present so I have committed this to the OG10 branch.
When this functionality is resubmitted for mainline, a proper review
will be required.
-Sandra
Sandra Loosemore (2):
Clean up loop variable extraction in OpenACC kernels loop annotation.
Relax some restrictions on the loop bound in
expression. This patch relaxes those
restrictions somewhat to allow many forms of expressions involving
such constants and variables, including calls to constant functions.
2020-08-30 Sandra Loosemore
gcc/c-family/
* c-omp.c (end_test_ok_for_annotation_r): New
I'll be posting those shortly and I hope to get those into GCC 11 as well.
-Sandra
On 8/13/20 10:34 AM, Sandra Loosemore wrote:
This is a revised version of the patch set originally posted
last November:
https://gcc.gnu.org/pipermail/gcc-patches/2019-November/534142.html
In addition to
be used to produce diagnostics about loops that cannot be
annotated.
2020-09-08 Sandra Loosemore
gcc/c-family/
* c-common.h (c_oacc_annotate_loops_in_kernels_regions): Declare.
* c-omp.c: Include tree-iterator.h.
(enum annotation_state): New.
(struct annot
581bdb6689d74c1849b7e6bc139c6f122fdcc2
16d59cea8362c1ec731aa5b4db42a2817f036f23
7b436e90a4e03fdce5b0c6a8c452d3f23f1e136b
c2789b61cf29397295f39a43f5d1605ab8a32d87
1c9af55d7ff76e2e6b633af33e6e6991a0ba4c48
20f37fd2f9c8c52fff380982d6fc5eb2d88b3dd9
df5f2065bad30dc6aff9653237157c33fd4161cd
Sandra Loosemore (2):
Kernels loops
front ends.
2020-09-08 Sandra Loosemore
Gergö Barany
gcc/fortran/
* gfortran.h (gfc_oacc_annotate_loops_in_kernels_regions):
Declare.
* lang.opt (Wopenacc-kernels-annotate-loops): New.
(fopenacc-kernels-annotate-loops): New.
* openmp.
On 9/9/20 3:13 PM, Jason Merrill wrote:
My impression from Jeff's analysis in January and David's in March was
that many of the testsuite changes were from the C++ approach actually
providing better results, so the reversal here surprises me. Can you
talk more about the regressions you're se
On 9/10/20 4:20 AM, Richard Biener wrote:
On Wed, Sep 9, 2020 at 7:55 PM Sandra Loosemore wrote:
This set of patches implements C/C++ and Fortran front end support for
adding "acc loop auto" annotations to loop nests in OpenACC kernels
regions. For background on this, refer
On 9/10/20 7:36 AM, David Malcolm wrote:
BTW, in terms of analyzer issues, my big rewrite of analyzer state-
tracking landed in master a month ago, on 2020-08-13 as
808f4dfeb3a95f50f15e71148e5c1067f90a126d, and changed the behavior of
gcc.dg/analyzer/explode-2.c, which was one of the ones an ear
On 2/11/20 7:46 AM, Roman Zhuykov wrote:
[snip]
Since I have to ask again about backports, I've decided to make few more
steps and with Alexander's help created new patch which rewords the
whole option description and covers items (3), (4) and (8). CCing Jakub
and Richard as release managers, al
On 2/20/20 3:08 PM, Jérémy Lefaure wrote:
Hello,
Ping for https://gcc.gnu.org/ml/gcc-patches/2019-12/msg01081.html.
Thank you,
Jérémy
On Sun, Dec 15, 2019 at 07:20:26PM +0100, Jérémy Lefaure wrote:
Hi!
Since in ARM state the value of PC is the address of the current
instruction plus 8 bytes,
d by
other tasks.
-Sandra
commit cf70bb0fbd7fb0f4bca99c53a36d0a389dcc2fc5
Author: Sandra Loosemore
Date: Wed Feb 26 19:51:06 2020 -0800
Document negative form of warning options enabled by default [PR90467].
2020-02-26 Sandra Loosemore
PR c++/90467
gcc/
* doc/invoke.texi (Option Summary)
On 1/27/20 2:02 PM, Jeff Law wrote:
[snip]
While I think we've missed the boat for gcc-10, I think these patches
should go forward in gcc-11. I'll own getting the paths sorted so that
this problem is avoided.
I recently retested these patches on trunk, and I found some new
regressions in t
ommit 86645c71b1ee8ca228a72a0c21ae38c4264da8fb
Author: Sandra Loosemore
Date: Sun Mar 22 10:22:59 2020 -0700
Test for sigsetjmp support in analyzer tests requiring that feature.
2020-03-22 Sandra Loosemore
gcc/testsuite/
* gcc.dg/analyzer/sigsetjmp-5.c: Require sigsetjmp su
t to avoid
optimizing the interesting things away, so I tweaked it to allow argc ==
0 in addition to argc == 1.
-Sandra
commit 0fca105f8ca95747fad3d3315e642ea9dc6936e0
Author: Sandra Loosemore
Date: Wed Mar 25 08:01:50 2020 -0700
Fix gcc.dg/pr92301.c on targets that don't support argc/argv.
1?
-Sandra
commit 3d2cda1e758a54111af04e80ea3dbaa27b3387e7
Author: Sandra Loosemore
Date: Wed Mar 25 21:29:17 2020 -0700
Bug fix for processing OpenACC data clauses in C++.
The C++ front end wraps the values in OpenACC data clause array range
specifications in NON_LVALUE_EXPR tree nodes. Th
On 7/9/20 3:57 AM, Tamar Christina wrote:
Hi All,
This document some of the existing DejaGnu directives to modify
environment variables before test or compiler invocations.
Bootstrapped Regtested on aarch64-none-linux-gnu and no issues.
Ok for master?
Thanks,
Tamar
gcc/ChangeLog:
*
over 10 seconds on this target. But, the
original numbers seem pretty random to me as well. Is there actually
any benefit to running more iterations even on a fast target?
-Sandra
commit 8163c5309d9663d75dbeadf7e04ab463c1c07f5d
Author: Sandra Loosemore
Date: Sun Jul 19 21:33:41 2020 -0700
dra
commit 2608a0ae0e81f039f354ec4c0c2fb0c3dbb8ea08
Author: Sandra Loosemore
Date: Mon Jul 20 16:02:53 2020 -0700
Scale down long-running tree-prof.exp tests for non-FDO testing.
2020-07-20 Sandra Loosemore
gcc/testsuite/
* lib/profopt.exp (auto-profopt-exec
On 8/4/20 2:46 AM, Jakub Jelinek wrote:
Hi!
When looking at the symver attr documentation in html, I found there is no
name to refer to for it.
The following patch fixes that, bootstrapped on x86_64-linux, ok for trunk
and 10.3?
2020-08-04 Jakub Jelinek
* doc/extend.texi (symver): A
On 3/26/20 8:27 AM, Thomas Schwinge wrote:
Hi!
Note that as this code is shared between OpenACC/OpenMP, this might
affect OpenMP, too, as far as I can tell. (Subject updated.) Jakub, can
you please have a look, too?
On 2020-03-25T23:02:38-0600, Sandra Loosemore wrote:
The attached patch
On 3/28/20 3:34 PM, H.J. Lu via Gcc-patches wrote:
Change -falign-functions=N to
Align the start of functions to the next power-of-two greater than
or equal to N.
Add
If '-falign-labels' is greater than this value, then its value is
used instead.
to -falign-loops=N and -fa
a950bb6e95236bb60ec17cda36763945d3d0a714
Author: Sandra Loosemore
Date: Thu Apr 2 13:37:58 2020 -0700
Fix check_effective_target_sigsetjmp for glibc targets.
2020-04-02 Sandra Loosemore
gcc/testsuite/
* lib/target-supports.exp (check_effective_target_sigsetjm
I noticed a bunch of comment typos in get_alias_set when I was reading
code to try to track down a bug affecting nios2 targets (see pr93946).
I've checked in this patch to clean them up.
-Sandra
commit 63f56527335a7667769b5dea15569e23d0ebc749
Author: Sandra Loosemore
Date: Thu Apr 2
: Sandra Loosemore
Date: Wed Apr 8 20:55:20 2020 -0700
Require pthread effective target for test case using -pthread option.
2020-04-08 Sandra Loosemore
gcc/testsuite/
* g++.dg/tree-ssa/pr93940.C: Require pthread target.
diff --git a/gcc/testsuite/ChangeLog b/gcc
On 4/21/20 1:26 AM, Iain Buclaw via Gcc-patches wrote:
Hi,
This patch adds documentation for --enable-libphobos-checking and
--with-libphobos-druntime-only options.
Does it read and explain clearly enough?
Regards
Iain.
gcc/ChangeLog:
* doc/install.texi (D-Specific Options): Document
On 4/27/20 9:08 AM, Matthias Kretz wrote:
@item -ffinite-math-only
@opindex ffinite-math-only
-Allow optimizations for floating-point arithmetic that assume
-that arguments and results are not NaNs or +-Infs.
+Assume that floating-point types in the language do not have representations
for
On 10/3/19 9:12 AM, Vladislav Ivanishin wrote:
Oh, and this old documentation bug. (AFAICT this is a historical
artifact from the pre-tree-ssa times when both -Wclobbered and
-Wuninitialized were implemented on RTL.)
This one is actually independent of the others and, I believe, is
obvious enou
On 10/3/19 9:16 AM, Bernd Edlinger wrote:
Hi,
I've noticed that the documentation of -Wshadow=x has some
missing bits, and I want to add an negative example to
-Wshadow=compatble-local.
Bootstrapped and reg-tested on x86_64-pc-linux-gnu.
Is it OK for trunk?
Index: gcc/doc/invoke.texi
=
On 10/8/19 2:52 AM, luoxhu wrote:
Hi,
This is the formal documentation patch for IPA passes. Thanks.
None of the IPA passes are documented in passes.texi. This patch adds
a section IPA passes just before GIMPLE passes and RTL passes in
Chapter 9 "Passes and Files of the Compiler". Also, a s
On 10/9/19 1:20 AM, Jan Hubicka wrote:
On Tue, Oct 8, 2019 at 10:06 PM Sandra Loosemore
wrote:
On 10/8/19 2:52 AM, luoxhu wrote:
Hi,
This is the formal documentation patch for IPA passes. Thanks.
None of the IPA passes are documented in passes.texi. This patch adds
a section IPA passes
On 10/12/19 12:10 PM, Bernd Edlinger wrote:
[snip snip]
So instead I'd like to adjust the doc of -Wshadow to reflect the implementation
and remove the if(warn_shadow_local) to have C and C++ behave identical and
hopefully now in sync with the doc.
Bootstrapped and reg-tested on x86_64-pc-linu
On 10/20/19 11:14 AM, Bernd Edlinger wrote:
Hi,
I've noticed that the description of -fcommon that gets printed
with "gcc -v --help" is exactly the opposite of what this
option actually does.
With -fcommon, different global variables w/o initial value
are plced in common blocks, similar to fort
before pushing it, since many of
us are going to be away until then anyway.
-Sandra
commit bde348ad056b57f97d581205e75d083b17a8d69c
Author: Sandra Loosemore
Date: Thu Dec 17 08:13:00 2020 -0800
Fortran: delinearize multi-dimensional array accesses
The Fortran front end present
On 1/4/21 4:15 AM, Matthew Malcomson wrote:
The original documentation added to mention the clash between
-fsanitize=address and -fsanitize=hwaddress used confusing wording trying to
say that -fsanitize=hwaddress is only available on AArch64.
It read as if -fsanitize=address were only supported
the loop nest with this patch which it did
not do without delinearization.
-Sandra
>From 2e714885f2aab9c24b6f3d37c995e7e4a5913ee5 Mon Sep 17 00:00:00 2001
From: Sandra Loosemore
Date: Thu, 7 Jan 2021 11:09:03 -0800
Subject: [PATCH] Fortran: delinearize multi-dimensional array accesses
The
On 1/14/21 12:16 PM, Sebastian Huber wrote:
The new -mcustom-fpu-cfg=fph2 option variant is useful to build a
multilib for the "Nios II Floating Point Hardware 2 Component":
https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/ug/ug_nios2_custom_instruction.pdf
Directly usin
On 1/14/21 12:16 PM, Sebastian Huber wrote:
This multilib supports Nios II configurations with the "Nios II Floating
Point Hardware 2 Component".
gcc/
* config/nios2/t-rtems: Reset all MULTILIB_* variables. Shorten
multilib directory names. Use MULTILIB_REQUIRED instead of
On 1/15/21 2:27 PM, Sebastian Huber wrote:
Hello Sandra,
On 15/01/2021 20:12, Sandra Loosemore wrote:
The following instructions supported by this component are not enabled
by this option:
* -mcustom-fmins
* -mcustom-fmaxs
* -mcustom-round
The reason is that these instructions are only in
On 1/16/21 1:23 AM, Sebastian Huber wrote:
Do not warn if custom instructions are not used due to missing
optimization flags. This prevents build errors with -Werror which
cannot be disabled via a dedicated warning option.
One reason to remove these warnings is to enable a multilib for the
"Nio
On 1/16/21 1:23 AM, Sebastian Huber wrote:
The new -mcustom-fpu-cfg=fph2 option variant is useful to build a
multilib for the "Nios II Floating Point Hardware 2 Component":
https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/ug/ug_nios2_custom_instruction.pdf
Directly using
On 1/16/21 1:23 AM, Sebastian Huber wrote:
This multilib supports Nios II configurations with the "Nios II Floating
Point Hardware 2 Component".
gcc/
* config/nios2/t-rtems: Reset all MULTILIB_* variables. Shorten
multilib directory names. Use MULTILIB_REQUIRED instead of
On 1/17/21 12:08 PM, Sebastian Huber wrote:
---
htdocs/gcc-11/changes.html | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 3527428f..dac3a03f 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gc
On 6/2/20 6:12 PM, Martin Sebor via Gcc-patches wrote:
The compute_objsize() function started out as a thin wrapper around
compute_builtin_object_size(), but over time developed its own
features to compensate for the other function's limitations (such
as its inability to work with ranges). The i
On 11/20/20 10:12 AM, Nathan Sidwell wrote:
@@ -214,14 +215,21 @@ in the following sections.
-faligned-new=@var{n} -fargs-in-order=@var{n} -fchar8_t -fcheck-new @gol
-fconstexpr-depth=@var{n} -fconstexpr-cache-depth=@var{n} @gol
-fconstexpr-loop-limit=@var{n} -fconstexpr-ops-limit=@var{n
On 9/9/20 11:53 AM, Sandra Loosemore wrote:
This set of patches implements C/C++ and Fortran front end support for
adding "acc loop auto" annotations to loop nests in OpenACC kernels
regions. For background on this, refer to Thomas Schwinge's talk from
last year's
On 11/11/22 13:52, Gerald Pfeifer wrote:
On Tue, 8 Nov 2022, Martin Liška wrote:
After the migration, people should be able to build (and install) GCC
even if they miss Sphinx (similar happens now if you miss makeinfo).
My nightly *install* (not build) on amd64-unknown-freebsd12.2 broke
(from
On 4/19/23 07:51, Frederik Harwath wrote:
Hi Sandra,
the OMP_FOR documentation says that the loop index variable
must be signed and it does not list "!=" in the allowed conditional
expressions. But there is nothing that would automatically cast an
unsigned variable
to signed or that converts th
. Frederik has
already reviewed my patches and gave me some very helpful feedback,
and Tobias also has helped out, especially when I got stuck on some
unrelated bugs.
-Sandra
Sandra Loosemore (3):
OpenMP: C support for imperfectly-nested loops
OpenMP: C++ support for imperfectly-nested
OpenMP 5.0 removed the restriction that multiple collapsed loops must
be perfectly nested, allowing "intervening code" (including nested
BLOCKs) before or after each nested loop. In GCC this code is moved
into the inner loop body by the respective front ends.
This patch changes the C front end to
OpenMP 5.0 removed the restriction that multiple collapsed loops must
be perfectly nested, allowing "intervening code" (including nested
BLOCKs) before or after each nested loop. In GCC this code is moved
into the inner loop body by the respective front ends.
This patch changes the C++ front end
OpenMP 5.0 removed the restriction that multiple collapsed loops must
be perfectly nested, allowing "intervening code" (including nested
BLOCKs) before or after each nested loop. In GCC this code is moved
into the inner loop body by the respective front ends.
In the Fortran front end, most of the
uilds, I'm not terribly enthusiastic about
trying to fix it this late in stage 4 even if it's technically
considered a documentation fix, so I've left that alone for now.
-Sandra
commit 5074c6fa38cef1abb9a355d717b41441a44c4e6a
Author: Sandra Loosemore
Date: Wed Mar
On 3/17/21 4:40 PM, Martin Sebor wrote:
[*] Does -Wformat-diag really trigger when using older GCC to build?
I thought it only triggered in stage 2 and 3 when using the same GCC
to rebuild itself.
I always end up hopelessly confused by anything involving configure
scripts and makefiles, but..
due to
placement of read-only symbols in .sdata instead of .srodata, some that
are likely general cross-compiler environment issues not specific to
nios2, and a few optimization failures which I haven't attempted to
analyze.)
-Sandra
commit 3cb9e3aee98a206b786d7414ad28e67fbcceba5c
Autho
On 6/17/21 10:03 AM, Tobias Burnus wrote:
Updated version – only lightly tested. I think it is
consistent like that and the documentation should now be
comprehensive. (I will have to do some additional testing.)
Further comments and thoughts?
Hmmm, I had started to put together some comment
On 6/17/21 1:40 PM, Jakub Jelinek wrote:
On Thu, Jun 17, 2021 at 09:28:00PM +0200, Tobias Burnus wrote:
I am not sure whether I fully agree with this or not. However:
Let's propose something radical, which probably won't break any real-world
code, avoids the need to add a new -foffload= keyword
On 6/17/21 5:05 PM, Tobias Burnus wrote:
On 17.06.21 23:57, Sandra Loosemore wrote:
On 6/17/21 1:40 PM, Jakub Jelinek wrote:
Could we introduce a different option which wouldn't imply enabling that
target:
-foffload-options==option
I think that works – in particular, if we do not doc
they have
all been fixed already except for this one.
OK to check in?
-Sandra
commit de9920753469e36c968b273a0e8b4d66a1d57946
Author: Sandra Loosemore
Date: Sun Jun 20 22:37:55 2021 -0700
Fortran: fix sm computation in CFI_allocate [PR93524]
This patch fixes a bug in settin
On 6/21/21 5:42 AM, Tobias Burnus wrote:
On 21.06.21 08:05, Sandra Loosemore wrote:
I ran into this bug in CFI_allocate while testing something else and
then realized there was already a PR open for it. It seems like an
easy fix, and I've used Tobias's test case from the issue mo
On 6/28/21 9:51 AM, Tobias Burnus wrote:
I managed to delete the libgomp part before posting the patch, hence,
reposted.
(The change from -foffload= to -foffload-options= ensures that also
other configured compilers such as GCN are used, an issue that Thomas
found. The original -foffload=nvpt
For the past several months I've been working on developing a set of
tests for the Fortran/C interoperability features added to Fortran via
TS 29113, "Further Interoperability of Fortran with C":
https://wg5-fortran.org/N1901-N1950/N1942.pdf
The goal here is to exercise gfortran's implementati
8ef11
Author: Sandra Loosemore
Date: Wed Jun 30 19:28:22 2021 -0700
Fortran: set version field in CFI_cdesc_t to CFI_VERSION
When converting a GFC descriptor to a CFI descriptor, it was
incorrectly copying the version number from the former to the latter.
It should be usin
On 7/1/21 11:08 AM, Tobias Burnus wrote:
Hi all,
this patch came up when discussing Sandra's TS29113 patch internally.
There is presumably also some overlap with José's patches.
This patch tries to rectify the BIND(C) CHARACTER handling on the
diagnostic side, only. That is: what to accept and
n nios2-elf and nios2-linux-gnu. I'm not set
up to test any of the other affected back ends, but the code change is
trivial and identical to what I did for nios2. OK to commit? I'd like
to backport this patch to all active branches as well, once it is in on
trunk.
-Sandra
2019-11-20 S
On 11/21/19 3:59 AM, Richard Sandiford wrote:
Sandra Loosemore writes:
This patch is for PR target/92499, a bug reported by GLIBC maintainers
against nios2 target. The initial failure symptom was a linker error
resulting from use of GP-relative addressing on an object that wasn't
allocat
is hardly any code that would be
affected if we did change the ABI down the road.
I plan to backport this patch to the GCC 9 branch but probably not any
older branches.
-Sandra
2019-12-01 Sandra Loosemore
Fix bugs relating to flexibly-sized objects in nios2 backend.
PR tar
Ping!
On 11/13/19 9:27 AM, Sandra Loosemore wrote:
This patch series lays some groundwork for the project to redo the
OpenACC "kernels" region support in GCC, described in Thomas
Schwinge's recent talk at the GNU Cauldron:
https://gcc.gnu.org/wiki/cauldron2019talks?action=Att
dified to defer processing of unmarked clones, and
anything left over is deleted.
OK to commit this along with the above-linked patch?
-SandraFrom bfffcea926d4dfb6275346237c61922a95c9e715 Mon Sep 17 00:00:00 2001
From: Sandra Loosemore
Date: Wed, 23 Nov 2022 23:14:31 +
Subject: [PATCH] [Op
On 12/1/22 20:29, Eric Gallager via Gcc-patches wrote:
A pretty simple patch; borrowed from Andrew Pinski on bugzilla:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59447
Tested by doing `./configure --help` in the gcc subdirectory and
noting that the "(or later)" made it into the output. OK for t
On 11/13/21 9:33 AM, H.J. Lu via Gcc-patches wrote:
Sync with binutils for building binutils with LTO:
From 50ad1254d5030d0804cbf89c758359ae202e8d55 Mon Sep 17 00:00:00 2001
From: "H.J. Lu"
Date: Sat, 9 Jan 2021 06:43:11 -0800
Subject: [PATCH] GCC: Pass --plugin to AR and RANLIB
Detect GCC LT
On 12/15/21 9:28 PM, H.J. Lu wrote:
I built nios2-linux-gnu cross compiler using glibc build-many-glibcs.py
script:
[snip]
using glibc master, binutils master and gcc master. Is there a way
to reproduce it with build-many-glibcs.py?
If it requires host tools built from binutils master, tha
I've checked in the attached patch to fix a testcase that's been failing
on nios2 for a while.
-Sandra
commit 840a22e0fee9e7369a2eb1c9e3c70dcae24a20e4
Author: Sandra Loosemore
Date: Thu Dec 16 15:17:14 2021 -0800
Testsuite: Tweak gcc.dg/20021029-1.c for nios2.
This
ry to fix all the test cases.
Tobias pointed me in this direction when I discussed it with him a few
weeks ago so I hope I got it right.
OK to check in? It regression-tests fine on x86_64.
-Sandra
commit 3a5e4f3a14b4265ee6f92dd724cbae9103d38d4b
Author: Sandra Loosemore
Date: Wed Dec 29 16:
435374884713a187ae8faa4eb
Author: Sandra Loosemore
Date: Tue Jan 4 18:18:13 2022 -0800
Fortran: Fix ICE caused by missing error for untyped symbol [PR103258]
The bit on a symbol to mark that it had already been diagnosed as
lacking a type was getting set even when th
Loosemore
Date: Wed Jan 5 13:18:10 2022 -0800
Fortran: Fix ICE in argument_rank_mismatch [PR103287]
This patch removes an incorrect assertion. A user-friendly error for this
case is already given elsewhere.
2022-01-05 Steve Kargl
Sandra Loosemore
PR
the logic.
OK to check in?
-Sandra
commit 0e5b74440572f988dd96a6e9c33c11b59323d6cf
Author: Sandra Loosemore
Date: Thu Jan 6 11:23:18 2022 -0800
Fortran: Fix handling of optional argument to SIZE intrinsic [PR103898]
This patch fixes a think-o in the code that triggered an ICE
bug was also reported to affect
powerpc. Anybody want to check it there? Otherwise, OK to check in?
-Sandra
commit bd91ec874339f9fd256b2d83de7159f6c11f
Author: Sandra Loosemore
Date: Sat Jan 8 19:59:26 2022 -0800
middle-end: move initialization of stack_limit_rtx [PR103163
I've checked in these tweaks for various testcases that fail on
nios2-elf without an explicit -fdelete-null-pointer-checks option. This
target is configured to build with that optimization off by default.
-Sandra
commit 04c69d0e61c0f98a010d77a79ab749d5f0aa6b67
Author: Sandra Loosemore
On 1/8/22 9:24 PM, Sandra Loosemore wrote:
This patch fixes the ICE I reported in PR103163. We were initializing
stack_limit_rtx before the register properties it depends on were
getting set. I moved it to the same function where stack_pointer_rtx,
frame_pointer_rtx, etc are being
On 1/17/22 1:29 AM, Richard Biener wrote:
On Mon, Jan 17, 2022 at 4:15 AM Sandra Loosemore
wrote:
On 1/8/22 9:24 PM, Sandra Loosemore wrote:
This patch fixes the ICE I reported in PR103163. We were initializing
stack_limit_rtx before the register properties it depends on were
getting set
examples that I haven't found a satisfactory way to fix yet
:-( but at least this patch is an incremental improvement.
-Sandracommit 35a80d19b69df59f52800f34bac1df3cb0293735
Author: Sandra Loosemore
Date: Thu Mar 16 21:05:53 2023 +
Docs: Fix some too-long lines in Texinfo m
ommit 7ffbc74c8c202a16a5e987134f03c2359c531f0e
Author: Sandra Loosemore
Date: Thu Mar 16 21:07:18 2023 +
Docs: Fix formatting issues in BPF built-ins documentation.
gcc/ChangeLog:
* doc/extend.texi (BPF Built-in Functions): Fix numerous markup
issues. Add more
On 3/16/23 16:37, Jonny Grant wrote:
Hello
There's a typo in the common function attribute docs, "nonnul" which this patch
corrects.
Thank you! I've pushed this patch.
-Sandra
On 3/20/23 14:05, Harald Anlauf via Gcc-patches wrote:
Dear all,
as reported, the implicit documentation of -funderscoring, which
is found under -fno-underscoring, has gone sideways long time ago.
The attached patch should fix it.
OK for mainline, or did I miss something?
This is OK.
-Sandra
On 3/18/23 14:14, Arsen Arsenović via Gcc-patches wrote:
Evening,
Ping on this patch series.
I believe we're close to being able to apply it, with contents of the
documentation changes being approved, and only a small build system
change and a revised patch series "shape" left to review.
Yup.
y doc maintainer superpowers and push this over the weekend if
I don't get any further technical comments about correctness meanwhile.
-Sandracommit 9a0fa0b9429882eca17849a64592b697ca4e2bf9
Author: Sandra Loosemore
Date: Tue Mar 21 22:15:33 2023 +
Docs, OpenMP: Correct internal docume
On 08/02/2018 04:27 PM, Jeff Law wrote:
I think the cse_cc pass is really just working around one or more bugs
in CSE and/or a backend bug. The RTL above clearly shows a common
subexpression that is not eliminated by CSE.
What CSE should be trying to do is changing the second and third
occurren
I've checked in this patch to fix the c-c++-common/spec-barrier-1.c test
failure on nios2. Per previous discussions about Spectre
vulnerabilities with Altera/Intel, this architecture is not affected so
no special handling is required here.
-Sandra
2018-08-03 Sandra Loosemore
that it does two different things, but I don't have any good
ideas for how to fix that.
Here's another attempt at documenting what's there now, this time
avoiding using the ambiguous term "custom" at all in the text. I've
also tried to address the other comments
This is the third iteration of the C-SKY port patch set. The previous
versions were posted here:
https://gcc.gnu.org/ml/gcc-patches/2018-07/msg01289.html
https://gcc.gnu.org/ml/gcc-patches/2018-07/msg01861.html
Changes since V2 are:
- The cse_cc pass is gone, replaced by a no-op move of the c
2018-08-05 Jojo
Huibin Wang
Sandra Loosemore
Chung-Lin Tang
Andrew Jenner
C-SKY port: Configury
gcc/
* config.gcc (csky-*-*): New.
* configure.ac: Add csky to targets for dwarf2 debug_line support.
* configure: Regenerated.
contrib/
* config-list.mk (LIST
2018-08-05 Jojo
Huibin Wang
Sandra Loosemore
Chung-Lin Tang
C-SKY port: Backend implementation
gcc/
* config/csky/*: New.
* common/config/csky/*: New.
csky-gcc-2.patch.gz
Description: application/gzip
2018-08-05 Sandra Loosemore
C-SKY port: Documentation
gcc/
* doc/extend.texi (C-SKY Function Attributes): New section.
* doc/invoke.texi (Option Summary): Add C-SKY options.
(C-SKY Options): New section.
* doc/md.texi (Machine Constraints): Document C-SKY constraints.
diff --git a/gcc
2018-08-05 Sandra Loosemore
Chung-Lin Tang
Xianmiao Qu
C-SKY port: Testsuite
gcc/testsuite/
* g++.dg/Wno-frame-address.C: Adjust for C-SKY.
* g++.dg/torture/type-generic-1.C: Likewise.
* gcc.c-torture/compile/2804-1.c: Likewise.
* gcc.c-torture/execute/20101011-1.c
2018-08-05 Jojo
Huibin Wang
Sandra Loosemore
Chung-Lin Tang
C-SKY port: libgcc
libgcc/
* config.host: Add C-SKY support.
* config/csky/*: New.
diff --git a/libgcc/config.host b/libgcc/config.host
index 18cabaf..bd4ef1e 100644
--- a/libgcc/config.host
+++ b/libgcc
401 - 500 of 1322 matches
Mail list logo
