This project is mirrored from git://gcc.gnu.org/git/gcc.git.
Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
- 25 May, 2020 1 commit
-
-
GCC Administrator authored
-
- 24 May, 2020 2 commits
-
-
GCC Administrator authored
- 23 May, 2020 1 commit
-
-
GCC Administrator authored
-
- 22 May, 2020 1 commit
-
-
GCC Administrator authored
-
- 21 May, 2020 5 commits
-
-
Martin Liska authored
gcc/ChangeLog: * common/config/aarch64/aarch64-common.c (aarch64_handle_option): Use MASK_OUTLINE_ATOMICS for x_target_flags.
-
Martin Liska authored
* common/config/aarch64/aarch64-common.c (aarch64_handle_option): Handle OPT_moutline_atomics. * config/aarch64/aarch64.c: Add outline-atomics to aarch64_attributes. * doc/extend.texi: Document the newly added target attribute. * gcc.target/aarch64/target_attr_20.c: New test. * gcc.target/aarch64/target_attr_21.c: New test. (cherry picked from commit 9e02b45f)
-
GCC Administrator authored
-
- 20 May, 2020 2 commits
-
-
Mark Eggleston authored
The value 'ppr@' is set in the name of result symbol, the actual name of the symbol is in the procedure name symbol pointed to by the result symbol's namespace (ns). When reporting errors for symbols that have the proc_pointer attribute check whether the result attribute is set and set the name accordingly. Backport from master. 2020-05-20 Mark Eggleston <markeggleston@gcc.gnu.org> gcc/fortran/ PR fortran/39695 * resolve.c (resolve_fl_procedure): Set name depending on whether the result attribute is set. For PROCEDURE/RESULT conflict use the name in sym->ns->proc_name->name. * symbol.c (gfc_add_type): Add check for function and result attributes use sym->ns->proc_name->name if both are set. Where the symbol cannot have a type use the name in sym->ns->proc_name->name. 2020-05-20 Mark Eggleston <markeggleston@gcc.gnu.org> gcc/testsuite/ PR fortran/39695 * gfortran.dg/pr39695_1.f90: New test. * gfortran.dg/pr39695_2.f90: New test. * gfortran.dg/pr39695_3.f90: New test. * gfortran.dg/pr39695_4.f90: New test. (cherry picked from commit eb069ae8)
-
GCC Administrator authored
-
- 19 May, 2020 1 commit
-
-
GCC Administrator authored
-
- 18 May, 2020 2 commits
-
-
Douglas Rupp authored
We're getting an error when running this test on PowerPC VxWorks 7, due to an unexpected warning: | Excess errors: | cc1: warning: '-mvsx' and '-mno-altivec' are incompatible The warning comes from a combination of factors: - The test itself uses -mvsx explicitly via the following directive: // { dg-options "-O1 -mvsx" } - Our toolchain was configured so as to make -mno-altivec the default; - These two options are mutually exclusive. This commit adds a powerpc_vsx_ok dg-require-effective-target directive to that test, and thus making it UNSUPPORTED instead. Tested on PowerPC VxWorks 7. Also tested on PowerPC ELF as well, a platform where we do not make -mno-altivec the default, to verify that the test continues to run as usual in that case. gcc/testsuite/ * gcc.target/powerpc/pr71763.c: Require powerpc_vsx_ok. (cherry picked from commit c917584a) -
GCC Administrator authored
-
- 17 May, 2020 1 commit
-
-
GCC Administrator authored
-
- 16 May, 2020 1 commit
-
-
GCC Administrator authored
-
- 15 May, 2020 1 commit
-
-
GCC Administrator authored
-
- 14 May, 2020 3 commits
-
-
Szabolcs Nagy authored
On aarch64 -mbranch-protection=pac-ret reuses the dwarf opcode for window_save to mean "toggle the return address mangle state", but in the dwarf2cfi internal logic the state was not updated when an opcode was emitted, the currently present update logic is only valid for the original sparc use of window_save so a separate bool is used on aarch64 to track the state. This bug can cause the unwinder not to authenticate return addresses that were signed (or vice versa) which means a runtime crash on a pauth enabled system. Currently only aarch64 pac-ret uses REG_CFA_TOGGLE_RA_MANGLE. This should be backported to gcc-9 and gcc-8 branches. Changed branch-protection=pac-ret to sign-return-address=all etc in the tests for the backport and adjusted the dwarf2cfi.c changes because the sparc change was missing. gcc/ChangeLog: Backport from mainline. 2020-04-27 Szabolcs Nagy <szabolcs.nagy@arm.com> PR target/94515 * dwarf2cfi.c (struct GTY): Add ra_mangled. (cfi_row_equal_p): Check ra_mangled. (dwarf2out_frame_debug_cfa_window_save): Remove the argument, this only handles the sparc logic now. (dwarf2out_frame_debug_cfa_toggle_ra_mangle): New function for the aarch64 specific logic. (dwarf2out_frame_debug): Update to use the new subroutines. (change_cfi_row): Check ra_mangled. gcc/testsuite/ChangeLog: Backport from mainline. 2020-04-27 Szabolcs Nagy <szabolcs.nagy@arm.com> PR target/94515 * g++.target/aarch64/pr94515-1.C: New test. * g++.target/aarch64/pr94515-2.C: New test.
-
Szabolcs Nagy authored
With -mbranch-protection=pac-ret the debug info toggles the signedness state of the return address so the unwinder knows when the return address needs pointer authentication. The unwind context flags were not updated according to the dwarf frame info. This causes unwinding across frames that were built without pac-ret to incorrectly authenticate the return address wich corrupts the return address on a system where PAuth is enabled. Note: This even affects systems where all code use pac-ret because unwinding across a signal frame the return address is not signed. Changed branch-protection=pac-ret to sign-return-address=all etc in the tests for the backport. gcc/testsuite/ChangeLog: Backport from mainline. 2020-04-23 Szabolcs Nagy <szabolcs.nagy@arm.com> PR target/94514 * g++.target/aarch64/pr94514.C: Require lp64. * gcc.target/aarch64/pr94514.c: Likewise. Backport from mainline. 2020-04-21 Szabolcs Nagy <szabolcs.nagy@arm.com> PR target/94514 * g++.target/aarch64/pr94514.C: New test. * gcc.target/aarch64/pr94514.c: New test. libgcc/ChangeLog: Backport from mainline. 2020-04-21 Szabolcs Nagy <szabolcs.nagy@arm.com> PR target/94514 * config/aarch64/aarch64-unwind.h (aarch64_frob_update_context): Update context->flags accroding to the frame state.
-
GCC Administrator authored
-
- 13 May, 2020 1 commit
-
-
GCC Administrator authored
-
- 12 May, 2020 2 commits
-
-
David Edelsohn authored
When long doubles are 64 bit, the AIX C library overrides the definitions but GCC builtins point to 128 bit names. This patch overrides the builtins for fmodl, frexpl, ldexpl and modfl to refer to the 64 bit symbols. Backport from mainline 2020-05-04 Clement Chigot <clement.chigot@atos.net> David Edelsohn <dje.gcc@gmail.com> * config/rs6000/rs6000-call.c (rs6000_init_builtins): Override expli cit for fmodl, frexpl, ldexpl and modfl builtins. -
GCC Administrator authored
-
- 11 May, 2020 2 commits
-
-
Mark Eggleston authored
This change is from a patch developed for gcc-5. The code has moved on since then requiring a change to interface.c 2020-05-11 Mark Eggleston <markeggleston@gcc.gnu.org> Backported from mainline 2020-05-11 Janus Weil <janus@gcc.gnu.org> Dominique d'Humieres <dominiq@lps.ens.fr> gcc/fortran/ PR fortran/59107 * gfortran.h: Rename field resolved as resolve_symbol_called and assign two 2 bits instead of 1. * interface.c (gfc_find_typebound_dtio_proc): Use new field name. * resolve.c (gfc_resolve_intrinsic): Replace check of the formal field with resolve_symbol_called is at least 2, if it is not set the field to 2. (resolve_symbol): Use new field name and check whether it is at least 1, if it is not set the field to 1. Backported from mainline 2020-05-11 Mark Eggleston <markeggleston@gcc.gnu.org> gcc/testsuite/ PR fortran/59107 * gfortran.dg/pr59107.f90: New test.
-
GCC Administrator authored
-
- 10 May, 2020 1 commit
-
-
GCC Administrator authored
-
- 09 May, 2020 1 commit
-
-
GCC Administrator authored
-
- 08 May, 2020 1 commit
-
-
GCC Administrator authored
-
- 07 May, 2020 2 commits
-
-
Uros Bizjak authored
Essentially the same fix as for x86. 2020-05-07 Uroš Bizjak <ubizjak@gmail.com> gcc/ * config/alpha/alpha.c (alpha_atomic_assign_expand_fenv): Use TARGET_EXPR instead of MODIFY_EXPR for the first assignments to fenv_var and new_fenv_var.
-
GCC Administrator authored
-
- 06 May, 2020 2 commits
-
-
Jonathan Wakely authored
* doc/xml/manual/abi.xml (abi.versioning.history): Update 8.0.0 to 8.1.0 in list of versions. * doc/html/*: Regenerate.
-
GCC Administrator authored
-
- 05 May, 2020 1 commit
-
-
GCC Administrator authored
-
- 04 May, 2020 6 commits
-
-
Jonathan Wakely authored
The previous URL to an entry in the wayback machine now redirects to a page saying "SGI.com Tech Archive Resources now retired" so use an older entry from the archive. * doc/xml/faq.xml: Use working link for SGI STL FAQ. * doc/html/*: Regenerate.
-
Eric Botcazou authored
This fixes a compilation error preventing bootstrap with Ada on x86_64-pc-cygwin. 2020-05-04 Mikael Pettersson <mikpelinux@gmail.com> PR bootstrap/94918 * mingw32.h: Prevent windows.h from including emmintrin.h on Cygw64.
-
Marek Polacek authored
PR c++/90736 - bogus error with alignof. * constexpr.c (adjust_temp_type): Use cv_unqualified type.
-
Bin Cheng authored
Precisely, for iv_use if it's not integer/pointer type, or non-mode precision type, add candidate for the corresponding scev in unsigned type with the same precision, rather than its original type. Backport from master. 2020-04-09 Bin Cheng <bin.cheng@linux.alibaba.com> PR tree-optimization/93674 gcc/ * tree-ssa-loop-ivopts.c (langhooks.h): New include. (add_iv_candidate_for_use): For iv_use of non integer or pointer type, or non-mode precision type, add candidate in unsigned type with the same precision. gcc/testsuite/ * g++.dg/pr93674.C: New test. -
Andreas Krebbel authored
The vector popcount expanders use a hardcoded subreg. This might lead to double subregs being generated which then fail to match. With this patch simplify_gen_subreg is used instead to fold the subregs. gcc/ChangeLog: 2020-05-04 Andreas Krebbel <krebbel@linux.ibm.com> Backport from mainline 2020-04-20 Andreas Krebbel <krebbel@linux.ibm.com> * config/s390/vector.md ("popcountv8hi2_vx", "popcountv4si2_vx") ("popcountv2di2_vx"): Use simplify_gen_subreg. gcc/testsuite/ChangeLog: 2020-05-04 Andreas Krebbel <krebbel@linux.ibm.com> Backport from mainline 2020-04-20 Andreas Krebbel <krebbel@linux.ibm.com> * g++.dg/pr94666.C: New test. -
Andreas Krebbel authored
The vsel instruction is a bit-wise select instruction. Using an IF_THEN_ELSE to express it in RTL is wrong and leads to wrong code being generated in the combine pass. With the patch the pattern is written using bit operations. However, I've just noticed that the manual still demands a fixed point mode for AND/IOR and friends although several targets emit bit ops on floating point vectors (including i386, Power, and s390). So I assume this is a safe thing to do?! gcc/ChangeLog: 2020-05-04 Andreas Krebbel <krebbel@linux.ibm.com> Backport from mainline 2020-04-20 Andreas Krebbel <krebbel@linux.ibm.com> PR target/94613 * config/s390/s390-builtin-types.def: Add 3 new function modes. * config/s390/s390-builtins.def: Add mode dependent low-level builtin and map the overloaded builtins to these. * config/s390/vx-builtins.md ("vec_selV_HW"): Rename to ... ("vsel<V_HW"): ... this and rewrite the pattern with bitops. gcc/testsuite/ChangeLog: 2020-05-04 Andreas Krebbel <krebbel@linux.ibm.com> Backport from mainline 2020-04-20 Andreas Krebbel <krebbel@linux.ibm.com> PR target/94613 * gcc.target/s390/zvector/pr94613.c: New test. * gcc.target/s390/zvector/vec_sel-1.c: New test.
-