public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Franz.Sirl-kernel@lauterbach.com To: gcc-gnats@gcc.gnu.org Cc: Andrew Haley <aph@cambridge.redhat.com> Subject: c/3665: ICE in merge_blocks_move_predecessor_nojumps, at flow.c:2341 Date: Thu, 12 Jul 2001 14:16:00 -0000 [thread overview] Message-ID: <20010712211421.31314.qmail@sourceware.cygnus.com> (raw) >Number: 3665 >Category: c >Synopsis: ICE in merge_blocks_move_predecessor_nojumps, at flow.c:2341 >Confidential: no >Severity: serious >Priority: high >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Thu Jul 12 14:16:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Franz.Sirl-kernel@lauterbach.com >Release: gcc-3.0, current gcc-3.0.1, current gcc-3.1 >Organization: >Environment: powerpc-linux-gnu, arm-linux-gnu >Description: The folllowing code snippet lets gcc-3.0 and gcc-3.0.1 ICE like that: [fsirl@enzo:/cvsx/rawhide/BUILD/unixODBC-2.0.7/Drivers/template]$ gcc -O2 -fPIC bug.c bug.c: In function `SQLSetConnectOption': bug.c:43: Internal compiler error in merge_blocks_move_predecessor_nojumps, at flow.c:2341 Please submit a full bug report, with preprocessed source if appropriate. See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions. With current gcc-3.1 CVS the ICE is different: [fsirl@entropy:~]$ ~/obj/gccm/gcc/stage1/xgcc -B ~/obj/gccm/gcc/stage1/ -O2 -fPIC -c flowbug.c flowbug.c: In function `SQLSetConnectOption': flowbug.c:42: Return not followed by barrier (jump_insn 152 151 71 (parallel[ (return) (use (reg:SI 65 lr)) ] ) -1 (nil) (nil)) flowbug.c:42: Internal compiler error in verify_flow_info, at flow.c:8082 Please submit a full bug report, with preprocessed source if appropriate. See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions. gcc-2.95.3 compiles this just fine, so this is a regression. >How-To-Repeat: compile with -O2 -fPIC: typedef struct tDRVDBC { void * hLog; } *HDRVDBC; int logPushMsg( void* hLog, char *pszModule, char *pszFunctionName, int nLine, int nSeverity, int nCode, char *pszMsg ); signed short int SQLSetConnectOption(void * hDrvDbc, unsigned short int nOption, unsigned long int vParam) { HDRVDBC hDbc = (HDRVDBC)hDrvDbc; if ( hDbc == 0 ) return (-2); switch ( nOption ) { case 106: case 107: case 110: case 104: switch ( vParam ) { case 1UL: case 0UL: default: ; } break; case 105: case 101: case 102: default: ; } logPushMsg( hDbc->hLog, "SQLSetConnectOption.c", "SQLSetConnectOption.c", 49, 1, 1, "SQL_SUCCESS_WITH_INFO Function not fully implemented" ); return 1; } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-07-12 14:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-12 14:16 Franz.Sirl-kernel [this message] 2001-07-20 5:19 hubicka 2002-03-26 10:36 Vladimir Kondratiev 2002-03-30 16:51 rth
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=20010712211421.31314.qmail@sourceware.cygnus.com \ --to=franz.sirl-kernel@lauterbach.com \ --cc=aph@cambridge.redhat.com \ --cc=gcc-gnats@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).