public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/114859] [14 Regression] Seeing new segmentation fault in same_type_as since r14-9752 Date: Fri, 26 Apr 2024 16:50:28 +0000 [thread overview] Message-ID: <bug-114859-4-fYuX3YAgaW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114859-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114859 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC| |pault at gcc dot gnu.org Priority|P3 |P2 Last reconfirmed| |2024-04-26 Target Milestone|--- |14.0 Summary|Seeing new segmentation |[14 Regression] Seeing new |fault in same_type_as |segmentation fault in | |same_type_as since r14-9752 --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Bisection shows the only change on that CU in that range is r14-9752-g35408b3669fac104cd380582b32e32c64a603d8b and the changes are mostly in the save_smoothers subroutine. diff -upb on the original dump between r14-9751 and r14-9752 is: --- amg_d_hierarchy_bld.f90.005t.original_ 2024-04-26 12:41:01.409999711 -0400 +++ amg_d_hierarchy_bld.f90.005t.original 2024-04-26 12:42:21.511060046 -0400 @@ -211,9 +211,6 @@ void restore_smoothers (struct amg_d_one __attribute__((fn spec (". . w w w "))) void save_smoothers (struct amg_d_onelev_type & restrict level, struct __class_amg_d_base_smoother_mod_Amg_d_base_smoother_type_a & restrict save1, struct __class_amg_d_base_smoother_mod_Amg_d_base_smoother_type_a & restrict save2, integer(kind=4) & restrict info) { - { - integer(kind=4) stat.18; - *info = 0; if (save1->_data != 0B) { @@ -328,7 +325,6 @@ void save_smoothers (struct amg_d_onelev } if (__builtin_expect ((integer(kind=8)) (stat.18 != 0), 0, 44)) goto L.34; (struct __vtype_amg_d_base_smoother_mod_Amg_d_base_smoother_type *) save1->_vptr = (struct __vtype_amg_d_base_smoother_mod_Amg_d_base_smoother_type *) level->sm._vptr; - (void) __builtin_memcpy ((void *) save1->_data, (void *) save1->_vptr->_def_init, (unsigned long) save1->_vptr->_size); L.34:; *info = stat.18; if (*info == 0) @@ -344,11 +340,11 @@ void save_smoothers (struct amg_d_onelev } } L.36:; - if (*info == 0 && level->sm2a._data != 0B) - { { integer(kind=4) stat.21; + if (*info == 0 && level->sm2a._data != 0B) + { if (__builtin_expect ((integer(kind=8)) (save2->_data != 0B), 0, 45)) { stat.21 = 5014; @@ -364,7 +360,6 @@ void save_smoothers (struct amg_d_onelev } if (__builtin_expect ((integer(kind=8)) (stat.21 != 0), 0, 44)) goto L.38; (struct __vtype_amg_d_base_smoother_mod_Amg_d_base_smoother_type *) save2->_vptr = (struct __vtype_amg_d_base_smoother_mod_Amg_d_base_smoother_type *) level->sm2a._vptr; - (void) __builtin_memcpy ((void *) save2->_data, (void *) save2->_vptr->_def_init, (unsigned long) save2->_vptr->_size); L.38:; *info = stat.21; if (*info == 0) @@ -384,15 +379,13 @@ void save_smoothers (struct amg_d_onelev } L.37:; return; - } } __attribute__((fn spec (". . . . w "))) void amg_d_hierarchy_bld (struct psb_dspmat_type & a, struct psb_desc_type & desc_a, struct __class_amg_d_prec_type_Amg_dprec_type_t & prec, integer(kind=4) & restrict info) { - static void restore_smoothers (struct amg_d_onelev_type &, struct __class_amg_d_base_smoother_mod_Amg_d_base_smoother_type_a & restrict, struct __class_amg_d_base_smoother_mod_Amg_d_base_smoother_type_a & restrict, integer(kind=4) & restrict); - static void save_smoothers (struct amg_d_onelev_type & restrict, struct __class_amg_d_base_smoother_mod_Amg_d_base_smoother_type_a & restrict, struct __class_amg_d_base_smoother_mod_Amg_d_base_smoother_type_a & restrict, integer(kind=4) & restrict); + integer(kind=4) stat.18; integer(kind=8) D.9689; integer(kind=8) D.9690; integer(kind=8) D.9691; so guess the only significant change is the removal of the two __builtin_memcpy calls.
next prev parent reply other threads:[~2024-04-26 16:50 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-26 3:59 [Bug fortran/114859] New: Seeing new segmentation fault in same_type_as orion at nwra dot com 2024-04-26 7:48 ` [Bug fortran/114859] " jakub at gcc dot gnu.org 2024-04-26 7:55 ` jakub at gcc dot gnu.org 2024-04-26 8:03 ` jakub at gcc dot gnu.org 2024-04-26 15:48 ` jakub at gcc dot gnu.org 2024-04-26 16:50 ` jakub at gcc dot gnu.org [this message] 2024-04-26 16:55 ` [Bug fortran/114859] [14 Regression] Seeing new segmentation fault in same_type_as since r14-9752 jakub at gcc dot gnu.org 2024-04-26 16:59 ` jakub at gcc dot gnu.org 2024-04-26 17:10 ` jakub at gcc dot gnu.org 2024-04-26 18:07 ` [Bug fortran/114859] [14/15 " jakub at gcc dot gnu.org 2024-04-26 18:27 ` jakub at gcc dot gnu.org 2024-04-27 14:50 ` pault at gcc dot gnu.org 2024-04-27 18:58 ` jakub at gcc dot gnu.org 2024-04-28 5:37 ` pault at gcc dot gnu.org 2024-04-28 21:19 ` pault at gcc dot gnu.org 2024-04-29 9:11 ` jakub at gcc dot gnu.org 2024-04-29 11:06 ` pault at gcc dot gnu.org 2024-04-29 18:45 ` anlauf at gcc dot gnu.org 2024-04-30 8:21 ` jakub at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-114859-4-fYuX3YAgaW@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).