public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/50514] gfortran should check ISHFT & ISHFTC aruments (r178939) Date: Sun, 25 Sep 2011 22:13:00 -0000 [thread overview] Message-ID: <bug-50514-4-N1gMl3joLJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50514-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50514 kargl at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kargl at gcc dot gnu.org --- Comment #1 from kargl at gcc dot gnu.org 2011-09-25 22:05:14 UTC --- Technically, it the programmer that should check the arguments. The prohibitions in the Fortran Standard are placed on the programmer not the Fortran processor (ie., the compiler). Adding the check into do i = 1,1000000 do j = 1, 1000000 do k = 1, 1000000 ! Some stuff here to compute k and n < bit_size(k) m = ishft(k,n) ! for some k, n ! More stuff here to use m end do end do end do seems like useless overhead.
next prev parent reply other threads:[~2011-09-25 22:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-25 20:07 [Bug fortran/50514] New: " zeccav at gmail dot com 2011-09-25 22:13 ` kargl at gcc dot gnu.org [this message] 2011-09-28 10:43 ` [Bug fortran/50514] " zeccav at gmail dot com 2011-09-28 20:03 ` sgk at troutmask dot apl.washington.edu 2011-09-29 7:56 ` zeccav at gmail dot com 2011-10-20 18:12 ` kargl 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-50514-4-N1gMl3joLJ@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).