public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "michael.haubenwallner at salomon dot at" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/46655] invalid '.line 0' directive emitted with -g Date: Mon, 29 Nov 2010 09:17:00 -0000 [thread overview] Message-ID: <bug-46655-4-p5wWgiwp4G@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46655-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46655 --- Comment #6 from Michael Haubenwallner <michael.haubenwallner at salomon dot at> 2010-11-29 09:05:53 UTC --- I'm in contact with IBM vi a customer's support channel - initially for another problem, and have added this 64k-line-limit recently. Although no reply yet, I'll add updates here when available.
next prev parent reply other threads:[~2010-11-29 9:06 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-25 10:08 [Bug target/46655] New: AIX6.1 native assembler requires '.line' numbers greater than zero michael.haubenwallner at salomon dot at 2010-11-25 10:50 ` [Bug target/46655] " michael.haubenwallner at salomon dot at 2010-11-25 11:19 ` [Bug target/46655] invalid '.line 0' directive emitted with -g ebotcazou at gcc dot gnu.org 2010-11-25 12:56 ` michael.haubenwallner at salomon dot at 2010-11-26 14:05 ` michael.haubenwallner at salomon dot at 2010-11-29 1:29 ` dje at gcc dot gnu.org 2010-11-29 9:17 ` michael.haubenwallner at salomon dot at [this message] 2010-11-29 10:02 ` ebotcazou at gcc dot gnu.org 2010-11-29 10:37 ` hainque at adacore dot com 2010-11-29 23:05 ` dje at gcc dot gnu.org 2010-11-30 12:53 ` michael.haubenwallner at salomon dot at 2010-11-30 15:43 ` michael.haubenwallner at salomon dot at 2010-11-30 15:48 ` dje at gcc dot gnu.org 2010-11-30 18:11 ` hainque at adacore dot com 2010-12-13 12:46 ` michael.haubenwallner at salomon dot at 2011-01-17 11:34 ` ebotcazou at gcc dot gnu.org 2011-01-17 12:47 ` ebotcazou at gcc dot gnu.org 2011-01-17 13:10 ` ebotcazou at gcc dot gnu.org 2011-01-17 13:21 ` ebotcazou at gcc dot gnu.org 2011-02-24 1:51 ` richard.nolde at cybox dot com 2011-02-24 9:45 ` ebotcazou at gcc dot gnu.org 2011-02-24 21:05 ` michael.haubenwallner at salomon dot at 2011-02-24 21:19 ` richard.nolde at cybox dot com 2011-02-24 22:39 ` richard.nolde at cybox dot com 2011-02-25 1:40 ` richard.nolde at cybox dot com 2011-02-25 10:13 ` michael.haubenwallner at salomon dot at 2011-02-25 10:20 ` michael.haubenwallner at salomon dot at 2011-02-25 18:43 ` dje at gcc dot gnu.org 2011-02-28 16:19 ` richard.nolde at cybox dot com 2011-04-01 12:25 ` michael.haubenwallner at salomon dot at 2011-05-17 5:44 ` richard.nolde at cybox dot com 2011-05-17 6:29 ` ebotcazou at gcc dot gnu.org 2011-05-17 7:52 ` michael.haubenwallner at salomon dot at
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-46655-4-p5wWgiwp4G@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).