public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vinaykumar.kondreddy at staples dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108982] While recompiling when even we modify any line in got its giving error Date: Wed, 01 Mar 2023 08:09:02 +0000 [thread overview] Message-ID: <bug-108982-4-WMkREMIaqm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108982-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108982 vinay kumar <vinaykumar.kondreddy at staples dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID |--- --- Comment #5 from vinay kumar <vinaykumar.kondreddy at staples dot com> --- Hi Richard Biener, We already contacted Oracle, but they are not suggesting anything for this GCC as it is freeware.
next prev parent reply other threads:[~2023-03-01 8:09 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-01 6:43 [Bug c/108982] New: " vinaykumar.kondreddy at staples dot com 2023-03-01 6:52 ` [Bug c/108982] " pinskia at gcc dot gnu.org 2023-03-01 6:52 ` pinskia at gcc dot gnu.org 2023-03-01 7:47 ` vinaykumar.kondreddy at staples dot com 2023-03-01 7:57 ` rguenth at gcc dot gnu.org 2023-03-01 8:09 ` vinaykumar.kondreddy at staples dot com [this message] 2023-03-01 9:03 ` jakub at gcc dot gnu.org 2023-03-01 9:10 ` vinaykumar.kondreddy at staples dot com 2023-03-01 9:14 ` jakub at gcc dot gnu.org 2023-03-01 17:17 ` vinaykumar.kondreddy at staples dot com 2023-03-01 17:18 ` pinskia at gcc dot gnu.org 2023-03-01 17:36 ` vinaykumar.kondreddy at staples dot com 2023-03-01 17:46 ` pinskia at gcc dot gnu.org 2023-03-01 17:58 ` vinaykumar.kondreddy at staples dot com 2023-03-01 18:07 ` pinskia at gcc dot gnu.org 2023-03-01 18:18 ` jakub at gcc dot gnu.org 2023-03-04 0:45 ` hp 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-108982-4-WMkREMIaqm@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).