public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/33720] A negative value in OpenMP clause num_threads is not detected at runtime Date: Wed, 19 Jun 2013 20:45:00 -0000 [thread overview] Message-ID: <bug-33720-4-8fuFsUTTvo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-33720-4@http.gcc.gnu.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 4302 bytes --] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33720 --- Comment #8 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #7) > I still believe it is not needed to slow down the runtime library with > checks for invalid programs. Negative num_threads is undefined behavior, > just don't do it. Perhaps the check could be added with the new -fsanitize=undefined? >From gcc-bugs-return-424664-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jun 19 20:46:09 2013 Return-Path: <gcc-bugs-return-424664-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 26318 invoked by alias); 19 Jun 2013 20:46:09 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 26301 invoked by uid 48); 19 Jun 2013 20:46:06 -0000 From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/57655] New: [4.8/4.9 Regression] ICE: in create_pre_exit, at mode-switching.c:418 with -mno-fp-ret-in-387 -mvzeroupper -mxop and __builtin_ilogbl() Date: Wed, 19 Jun 2013 20:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: zsojka at seznam dot cz X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: <bug-57655-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-06/txt/msg01043.txt.bz2 Content-length: 2033 http://gcc.gnu.org/bugzilla/show_bug.cgi?idW655 Bug ID: 57655 Summary: [4.8/4.9 Regression] ICE: in create_pre_exit, at mode-switching.c:418 with -mno-fp-ret-in-387 -mvzeroupper -mxop and __builtin_ilogbl() Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: zsojka at seznam dot cz Created attachment 30324 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id0324&actioníit reduced testcase Compiler output: $ gcc -mno-fp-ret-in-387 -mvzeroupper -mxop testcase.c testcase.c: In function 'foo': testcase.c:5:1: internal compiler error: in create_pre_exit, at mode-switching.c:418 } ^ 0x1178ceb create_pre_exit /mnt/svn/gcc-trunk/gcc/mode-switching.c:404 0x1178ceb optimize_mode_switching /mnt/svn/gcc-trunk/gcc/mode-switching.c:493 0x1178ceb rest_of_handle_mode_switching /mnt/svn/gcc-trunk/gcc/mode-switching.c:779 0xc97d17 rest_of_handle_insert_vzeroupper /mnt/svn/gcc-trunk/gcc/config/i386/i386.c:2599 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions. $ gcc -v Using built-in specs. COLLECT_GCC=/mnt/svn/gcc-trunk/binary-latest/bin/gcc COLLECT_LTO_WRAPPER=/mnt/svn/gcc-trunk/binary-200176-lto-fortran-checking-yes-rtl-df/libexec/gcc/x86_64-unknown-linux-gnu/4.9.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: /mnt/svn/gcc-trunk//configure --enable-checking=yes,rtl,df --enable-languages=c,c++,lto,fortran --prefix=/mnt/svn/gcc-trunk/binary-200176-lto-fortran-checking-yes-rtl-df/ --without-cloog --without-ppl Thread model: posix gcc version 4.9.0 20130618 (experimental) (GCC) Tested revisions: r200211 - ICE 4.8 r198018 - ICE 4.7 r198018 - OK
next prev parent reply other threads:[~2013-06-19 20:45 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-33720-4@http.gcc.gnu.org/bugzilla/> 2013-06-19 18:19 ` geir at cray dot com 2013-06-19 18:23 ` jakub at gcc dot gnu.org 2013-06-19 20:45 ` manu at gcc dot gnu.org [this message] 2021-12-29 7:54 ` pinskia at gcc dot gnu.org 2007-10-09 20:49 [Bug c/33720] New: A negative value in OpenMP clause num_threasds " geir at cray dot com 2007-11-12 19:37 ` [Bug libgomp/33720] A negative value in OpenMP clause num_threads " jakub at gcc dot gnu dot org 2008-08-07 2:56 ` manu at gcc dot gnu dot org 2009-07-31 15:12 ` manu at gcc dot gnu dot org 2009-09-14 20:00 ` geir at cray dot com
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-33720-4-8fuFsUTTvo@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).