public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/98577] Wrong "count_rate" values with int32 and real32 if the "count" argument is int64. Date: Fri, 08 Jan 2021 19:19:22 +0000 [thread overview] Message-ID: <bug-98577-4-7Jo4LVUpOu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98577-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98577 --- Comment #19 from Steve Kargl <sgk at troutmask dot apl.washington.edu> --- On Fri, Jan 08, 2021 at 06:43:20PM +0000, mehdi.chinoune at hotmail dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98577 > > --- Comment #17 from Chinoune <mehdi.chinoune at hotmail dot com> --- > Once I reported a bug to gcc/gfortran > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91337 but someone argued that it > was my fault to use "-Ofast" so I rewrite the reproducer in C and reported > again under another category > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91734. the bug was confirmed and > fixed without someone blaming me for that. Fortran and C are different languages. I standby my assessment. Options that cause the compiler to knowingly violate the Fortran Standard and cause unexpected behavior do not justify a bug. > Another when I reported another bug but that "someone" said that my reproducer > is invalid, fortunately some other guys didn't take his opinion under > consideration and they fixed the bug. > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92736 Well, I actually I never stated the code was invalid. In comment #1, I said I "Not sure the code is conforming, and don't have time to investigate (unless someone is willing to cough up $$)." Also, suggested two workarounds that would get you passed the issue. In comment #2, you stated "You introduced a regression and it is your duty to fix it." In comment #3, I clearly stated "When it comes to gfortran, I have no duty to you or anyone else. I have neither the time nor now the inclination to look at this bug (unless someone coughs up $$$$ (price just went up ;))." At this point, I stopped looking at the bug because I have a real job that pays me $ to feed my family, and I found the tone of your comment #3 to b rude. So, in summary you once again are bending what is written to your reality. > The problem is that "someone" still there (fortran category) > attacking anyone who dare to report a bug in gfortran. You are not being attacked. You are being educated on what processor-dependent behavior means, and you have been told that the gfortran documentation tells you what the processor-dependent behavior is. If you refuse to learn, neither I nor anyone else can help you.
next prev parent reply other threads:[~2021-01-08 19:19 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-07 4:12 [Bug fortran/98577] New: " mehdi.chinoune at hotmail dot com 2021-01-07 11:36 ` [Bug fortran/98577] " anlauf at gcc dot gnu.org 2021-01-07 13:03 ` mehdi.chinoune at hotmail dot com 2021-01-07 16:32 ` kargl at gcc dot gnu.org 2021-01-07 17:28 ` mehdi.chinoune at hotmail dot com 2021-01-07 18:01 ` sgk at troutmask dot apl.washington.edu 2021-01-07 18:49 ` mehdi.chinoune at hotmail dot com 2021-01-07 18:56 ` mehdi.chinoune at hotmail dot com 2021-01-07 20:27 ` sgk at troutmask dot apl.washington.edu 2021-01-07 20:37 ` kargl at gcc dot gnu.org 2021-01-08 6:18 ` mehdi.chinoune at hotmail dot com 2021-01-08 7:21 ` kargl at gcc dot gnu.org 2021-01-08 8:04 ` mehdi.chinoune at hotmail dot com 2021-01-08 8:27 ` mehdi.chinoune at hotmail dot com 2021-01-08 16:12 ` kargl at gcc dot gnu.org 2021-01-08 16:42 ` mehdi.chinoune at hotmail dot com 2021-01-08 16:59 ` kargl at gcc dot gnu.org 2021-01-08 18:43 ` mehdi.chinoune at hotmail dot com 2021-01-08 18:55 ` sgk at troutmask dot apl.washington.edu 2021-01-08 19:19 ` sgk at troutmask dot apl.washington.edu [this message] 2021-01-09 2:34 ` mehdi.chinoune at hotmail dot com 2021-01-09 3:43 ` kargl at gcc dot gnu.org 2021-01-09 9:00 ` tkoenig at gcc dot gnu.org 2023-05-14 16:01 ` mehdi.chinoune at hotmail dot com 2023-05-14 16:37 ` tkoenig 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-98577-4-7Jo4LVUpOu@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).