public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/112404] [14 Regression] 521.wrf_r fails to build with internal compiler error: in get_vectype_for_scalar_type, at tree-vect-stmts.cc:13311 Date: Mon, 06 Nov 2023 11:17:36 +0000 [thread overview] Message-ID: <bug-112404-4-vx5AhkRFCZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112404-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112404 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Target Milestone|--- |14.0 Status|UNCONFIRMED |ASSIGNED Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Mine. SUBROUTINE sfddagd( regime, znt ,ite ,jte ) REAL, DIMENSION( ime, IN) :: regime, znt REAL, DIMENSION( ite, jte) :: wndcor_u LOGICAL wrf_dm_on_monitor IF( int4 == 1 ) THEN DO j=jts,jtf DO i=itsu,itf reg = regime(i-1, j) IF( reg > 10.0 ) THEN znt0 = znt(i-1, j) + znt(i, j) IF( znt0 <= 0.2) THEN wndcor_u(i,j) = 0.2 ENDIF ENDIF ENDDO ENDDO IF ( wrf_dm_on_monitor()) THEN ENDIF ENDIF END
next prev parent reply other threads:[~2023-11-06 11:17 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-06 10:45 [Bug tree-optimization/112404] New: " rguenth at gcc dot gnu.org 2023-11-06 11:16 ` [Bug tree-optimization/112404] " tnfchris at gcc dot gnu.org 2023-11-06 11:17 ` rguenth at gcc dot gnu.org [this message] 2023-11-06 11:39 ` rguenth at gcc dot gnu.org 2023-11-06 13:09 ` cvs-commit at gcc dot gnu.org 2023-11-06 13:10 ` rguenth at gcc dot gnu.org 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-112404-4-vx5AhkRFCZ@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).