public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/111859] New: 521.wrf_r build failure with -O2 -march=cascadelake  --param vect-partial-vector-usage=2
Date: Wed, 18 Oct 2023 08:17:39 +0000	[thread overview]
Message-ID: <bug-111859-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111859

            Bug ID: 111859
           Summary: 521.wrf_r build failure with -O2 -march=cascadelake
                    --param vect-partial-vector-usage=2
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: crazylht at gmail dot com
  Target Milestone: ---
            Target: x86_64-*-* i?86-*-*

Created attachment 56136
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56136&action=edit
reproduce source code

internal compiler error: in get_vectype_for_scalar_type, at
tree-vect-stmts.cc:13153                                                      
 20xe07a6d get_vectype_for_scalar_type(vec_info*, tree_node*, unsigned int)     
 3        ../gcc/tree-vect-stmts.cc:13153                                       
 40x277afe1 get_mask_type_for_scalar_type(vec_info*, tree_node*, unsigned int)  
 5        ../gcc/tree-vect-stmts.cc:13223                                       
 60x277afe1 vect_check_scalar_mask                                              
 7        ../gcc/tree-vect-stmts.cc:2450                                        
 80x277b584 vectorizable_call                                                   
 9        ../gcc/tree-vect-stmts.cc:3480                                        
100x278ceaf vect_analyze_stmt(vec_info*, _stmt_vec_info*, bool*, _slp_tree*,
_slp_instance*, vec<stmt_info_for_cost, va_heap, vl_ptr>*)     
11        ../gcc/tree-vect-stmts.cc:12785                                       
120x18b0430 vect_slp_analyze_node_operations_1                                  
13        ../gcc/tree-vect-slp.cc:6066                                          
140x18b0430 vect_slp_analyze_node_operations                                    
15        ../gcc/tree-vect-slp.cc:6265                                          
160x18b0364 vect_slp_analyze_node_operations                                    
17        ../gcc/tree-vect-slp.cc:6244                                          
180x18b20fb vect_slp_analyze_operations(vec_info*)                              
19        ../gcc/tree-vect-slp.cc:6516                                          
200x18b8792 vect_slp_analyze_bb_1                                               
21        ../gcc/tree-vect-slp.cc:7520                                          
220x18b8792 vect_slp_region                                                     
23        ../gcc/tree-vect-slp.cc:7567                                          
240x18ba7e9 vect_slp_bbs                                                        
25        ../gcc/tree-vect-slp.cc:7775                                          
260x18bab5b vect_slp_function(function*)                                        
27        ../gcc/tree-vect-slp.cc:7854                                          
280x18c4ee1 execute                                                             
29        ../gcc/tree-vectorizer.cc:1529                                        
30Please submit a full bug report, with preprocessed source (by using
-freport-bug).                                                        
31Please include the complete backtrace with any bug report.                    
32See <https://gcc.gnu.org/bugs/> for instructions.

             reply	other threads:[~2023-10-18  8:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18  8:17 crazylht at gmail dot com [this message]
2023-10-18  8:19 ` [Bug tree-optimization/111859] " crazylht at gmail dot com
2023-11-12 23:27 ` pinskia 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-111859-4@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: link
Be 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).