aboutsummaryrefslogtreecommitdiff
path: root/gcc
AgeCommit message (Collapse)AuthorFilesLines
2023-03-16Daily bump.GCC Administrator1-1/+1
2023-03-15Daily bump.GCC Administrator1-1/+1
2023-03-14Daily bump.GCC Administrator1-1/+1
2023-03-13Daily bump.GCC Administrator1-1/+1
2023-03-12Daily bump.GCC Administrator1-1/+1
2023-03-11Daily bump.GCC Administrator1-1/+1
2023-03-10Daily bump.GCC Administrator1-1/+1
2023-03-09Daily bump.GCC Administrator1-1/+1
2023-03-08Daily bump.GCC Administrator1-1/+1
2023-03-07Daily bump.GCC Administrator1-1/+1
2023-03-06Daily bump.GCC Administrator3-1/+55
2023-03-05Fortran: fix corner case of IBITS intrinsic [PR108937]Harald Anlauf2-0/+42
gcc/fortran/ChangeLog: PR fortran/108937 * trans-intrinsic.c (gfc_conv_intrinsic_ibits): Handle corner case LEN argument of IBITS equal to BITSIZE(I). gcc/testsuite/ChangeLog: PR fortran/108937 * gfortran.dg/ibits_2.f90: New test. (cherry picked from commit 6cce953ebec274f1468d5d3a0697cf05bb43b8f6)
2023-03-05Fortran: reject invalid CHARACTER length of derived type components [PR96024]Harald Anlauf2-0/+24
gcc/fortran/ChangeLog: PR fortran/96024 * resolve.c (resolve_component): The type of a CHARACTER length expression must be INTEGER. gcc/testsuite/ChangeLog: PR fortran/96024 * gfortran.dg/pr96024.f90: New test. (cherry picked from commit 31303c9b5bab200754cdb7ef8cd91ae4918f3018)
2023-03-05Fortran: improve checking of character length specification [PR96025]Harald Anlauf3-12/+28
gcc/fortran/ChangeLog: PR fortran/96025 * parse.c (check_function_result_typed): Improve type check of specification expression for character length and return status. (parse_spec): Use status from above. * resolve.c (resolve_fntype): Prevent use of invalid specification expression for character length. gcc/testsuite/ChangeLog: PR fortran/96025 * gfortran.dg/pr96025.f90: New test. (cherry picked from commit 6c1b825b3d6499dfeacf7c79dcf4b56a393ac204)
2023-03-05Daily bump.GCC Administrator1-1/+1
2023-03-04Daily bump.GCC Administrator3-1/+21
2023-03-03d: Fix ICE on explicit immutable struct import [PR108877]Iain Buclaw3-1/+22
Const and immutable types are built as variants of the type they are derived from, and TYPE_STUB_DECL is not set for these variants. PR d/108877 gcc/d/ChangeLog: * imports.cc (ImportVisitor::visit (EnumDeclaration *)): Call make_import on TYPE_MAIN_VARIANT. (ImportVisitor::visit (AggregateDeclaration *)): Likewise. (ImportVisitor::visit (ClassDeclaration *)): Likewise. gcc/testsuite/ChangeLog: * gdc.dg/imports/pr108877a.d: New test. * gdc.dg/pr108877.d: New test. (cherry picked from commit ce1cea3e22f58bbddde017f8a92e59bae8892339)
2023-03-03Daily bump.GCC Administrator1-1/+1
2023-03-02Daily bump.GCC Administrator1-1/+1
2023-03-01Daily bump.GCC Administrator1-1/+1
2023-02-28Daily bump.GCC Administrator1-1/+1
2023-02-27Daily bump.GCC Administrator1-1/+1
2023-02-26Daily bump.GCC Administrator1-1/+1
2023-02-25Daily bump.GCC Administrator2-1/+9
2023-02-24RTEMS: Tune multilib selectionSebastian Huber1-8/+9
gcc/ChangeLog: * config/riscv/t-rtems: Keep only -mcmodel=medany 64-bit multilibs. Add non-compact 32-bit multilibs. (cherry picked from commit 35a067020e41d97bc3be15b518b3dc2a64b4aae2)
2023-02-24Daily bump.GCC Administrator1-1/+1
2023-02-23Daily bump.GCC Administrator1-1/+1
2023-02-22Daily bump.GCC Administrator1-1/+1
2023-02-21Daily bump.GCC Administrator3-1/+20
2023-02-20aarch64: Fix up bfmlal lane pattern [PR104921]Alex Coplan4-1/+28
As the testcase shows, this pattern had an incorrect constraint leading to GCC's output getting rejected by the assembler. This patch fixes the constraint accordingly. The test is split into two: one that can run without bf16 support from the assembler and another that checks that the output actually assembles when such support is available. gcc/ChangeLog: PR target/104921 * config/aarch64/aarch64-simd.md (aarch64_bfmlal<bt>_lane<q>v4sf): Use correct constraint for operand 3. gcc/testsuite/ChangeLog: PR target/104921 * gcc.target/aarch64/pr104921-1.c: New test. * gcc.target/aarch64/pr104921-2.c: New test. * gcc.target/aarch64/pr104921.x: Include file for new tests. (cherry picked from commit 277e1f30a5e4e634304a7b8a532825119f0ea47f)
2023-02-20Daily bump.GCC Administrator1-1/+1
2023-02-19Daily bump.GCC Administrator1-1/+1
2023-02-18Daily bump.GCC Administrator1-1/+1
2023-02-17Daily bump.GCC Administrator1-1/+1
2023-02-16Daily bump.GCC Administrator1-1/+1
2023-02-15Daily bump.GCC Administrator1-1/+1
2023-02-14Daily bump.GCC Administrator3-1/+40
2023-02-12rs6000: Teach rs6000_opaque_type_invalid_use_p about gcall [PR108348]Kewen Lin3-4/+61
PR108348 shows one special case that MMA opaque types are used in function arguments and treated as pass by reference, it results in one copying from argument to a temp variable, since this copying happens before rs6000_function_arg check, it can cause ICE without MMA support then. This patch is to teach function rs6000_opaque_type_invalid_use_p to check if any function argument in a gcall stmt has the invalid use of MMA opaque types. btw, I checked the handling on return value, it doesn't have this kind of issue as its checking and error emission is quite early, so this doesn't handle function return value. PR target/108348 gcc/ChangeLog: * config/rs6000/rs6000.c (rs6000_opaque_type_invalid_use_p): Add the support for invalid uses of MMA opaque type in function arguments. gcc/testsuite/ChangeLog: * gcc.target/powerpc/pr108348-1.c: New test. * gcc.target/powerpc/pr108348-2.c: New test. (cherry picked from commit 5d9529687deb9ed009361a16c02a7f6c3e2ebbf3)
2023-02-12rs6000: Teach rs6000_opaque_type_invalid_use_p about inline asm [PR108272]Kewen Lin5-10/+112
As PR108272 shows, there are some invalid uses of MMA opaque types in inline asm statements. This patch is to teach the function rs6000_opaque_type_invalid_use_p for inline asm, check and error any invalid use of MMA opaque types in input and output operands. PR target/108272 gcc/ChangeLog: * config/rs6000/rs6000.c (rs6000_opaque_type_invalid_use_p): Add the support for invalid uses in inline asm, factor out the checking and erroring to lambda function check_and_error_invalid_use. gcc/testsuite/ChangeLog: * gcc.target/powerpc/pr108272-1.c: New test. * gcc.target/powerpc/pr108272-2.c: New test. * gcc.target/powerpc/pr108272-3.c: New test. * gcc.target/powerpc/pr108272-4.c: New test. (cherry picked from commit 074b0c03eabeb8e9c8de813c81bf87a1f88fdb65)
2023-02-13Daily bump.GCC Administrator1-1/+1
2023-02-12Daily bump.GCC Administrator3-1/+57
2023-02-11Fortran: ASSOCIATE variables should not be TREE_STATIC [PR95107]Harald Anlauf2-0/+18
gcc/fortran/ChangeLog: PR fortran/95107 * trans-decl.c (gfc_finish_var_decl): With -fno-automatic, do not make ASSOCIATE variables TREE_STATIC. gcc/testsuite/ChangeLog: PR fortran/95107 * gfortran.dg/save_7.f90: New test. (cherry picked from commit c36f3da534e7f411c5bc48c5b6b660e238167480)
2023-02-11Fortran: error recovery on invalid array section [PR108609]Harald Anlauf2-2/+6
The testcase for PR108527 uncovered a latent issue with invalid array sections that resulted in different paths being taken on different architectures. Detect the invalid array declaration for a clean recovery. gcc/fortran/ChangeLog: PR fortran/108609 * expr.c (find_array_section): Add check to prevent interpreting an mpz non-integer constant as an integer. gcc/testsuite/ChangeLog: PR fortran/108609 * gfortran.dg/pr108527.f90: Adjust test pattern. (cherry picked from commit 88a2a09dd4529107e7ef7a6e7ce43acf96457173)
2023-02-11Fortran: fix ICE in compare_bound_int [PR108527]Harald Anlauf2-15/+24
gcc/fortran/ChangeLog: PR fortran/108527 * resolve.c (compare_bound_int): Expression to compare must be of type INTEGER. (compare_bound_mpz_t): Likewise. (check_dimension): Fix comment on checks applied to array section and clean up associated logic. gcc/testsuite/ChangeLog: PR fortran/108527 * gfortran.dg/pr108527.f90: New test. Co-authored-by: Steven G. Kargl <kargl@gcc.gnu.org> (cherry picked from commit 22afa4947584c701633a79fd8750c9ceeaa96711)
2023-02-11Daily bump.GCC Administrator1-1/+1
2023-02-10Daily bump.GCC Administrator1-1/+1
2023-02-09Daily bump.GCC Administrator1-1/+1
2023-02-08Daily bump.GCC Administrator3-1/+18
2023-02-07tree-optimization/106809 - compile time hog in VNRichard Biener2-27/+58
The dominated_by_p_w_unex function is prone to high compile time. With GCC 12 we introduced a VN run for uninit diagnostics which now runs into a degenerate case with bison generated code. Fortunately this case is easy to fix with a simple extra check - a more general fix needs more work. PR tree-optimization/106809 * tree-ssa-sccvn.c (dominaged_by_p_w_unex): Check we have more than one successor before doing extra work. * gcc.dg/torture/pr106809.c: New testcase. (cherry picked from commit be1b42de9c151d46c89f9a8f82d4c5839a19ea94)
2023-02-07Daily bump.GCC Administrator1-1/+1
generated by cgit v1.1 at 2025-09-20 21:54:08 +0000