https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106707
--- Comment #4 from Xionghu Luo (luoxhu at gcc dot gnu.org) ---
Maybe guard the pattern with...
diff --git a/gcc/config/i386/i386.md b/gcc/config/i386/i386.md
index 58fcc382fa2..2a9d70da6d0 100644
--- a/gcc/config/i386/i386.md
+++ b/gcc/config/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91085
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |10.5
Summary|fixincludes brea
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106717
Bug ID: 106717
Summary: [13 Regression] ICE: tree check: expected integer_cst,
have poly_int_cst in get_len, at tree.h:6247
Product: gcc
Version: 13.0
Status: UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106099
--- Comment #11 from Zdenek Sojka ---
And with another degenerate flags on the testcase above:
# x86_64-pc-linux-gnu-gcc -O -fno-tree-forwprop -fno-tree-dominator-opts
-fharden-conditional-branches -funreachable-traps -fno-tree-ccp
--param=max-l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106716
--- Comment #2 from Tomer Vromen ---
IMO, attribute information should be checked in this optimization stage, so
that ipa-icf knows the functions are different. It seems like maybe this is
already partially the behavior - removing the attribute
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106716
--- Comment #3 from Andrew Pinski ---
[[unlikely]]/[[likely]] attribute gets expanded into
PREDICT_EXPR:PRED_HOT_LABEL/PRED_COLD_LABEL:TAKEN/NOT_TAKEN see
cp/cp-gimplify.cc (process_stmt_hotness_attribute) and is removed.
And that is all done i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106718
Bug ID: 106718
Summary: Behavior does not follow the standard for DW_AT_ranges
and DW_FORM_sec_offset
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106719
Bug ID: 106719
Summary: '-fcompare-debug' failure w/ -O2
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: compare-debug-failure
Severity: normal
Priori
101 - 108 of 108 matches
Mail list logo