public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "imran.siddiqui at live dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/65920] Not able to compile a code Date: Tue, 28 Apr 2015 20:41:00 -0000 [thread overview] Message-ID: <bug-65920-4-CqCaSrUa61@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65920-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65920 Imran <imran.siddiqui at live dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID |--- --- Comment #2 from Imran <imran.siddiqui at live dot com> --- Thans for the quick reply. The code is perfectly fine as it was workinng as i mentioned earlier But after the upgrade only it started throwing the error. I tried repalcing char * with string in the log.cpp..but again it left me some other errors
next prev parent reply other threads:[~2015-04-28 20:41 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-28 20:28 [Bug c/65920] New: " imran.siddiqui at live dot com 2015-04-28 20:34 ` [Bug c/65920] " pinskia at gcc dot gnu.org 2015-04-28 20:41 ` imran.siddiqui at live dot com [this message] 2015-04-28 20:56 ` [Bug c++/65920] " pinskia 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-65920-4-CqCaSrUa61@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).