public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/46405] Preprocessor generated code can exceed 132 characters Date: Sun, 14 Nov 2010 19:10:00 -0000 [thread overview] Message-ID: <bug-46405-4-ePBAhbeKoA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46405-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46405 Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jvdelisle at gcc dot | |gnu.org --- Comment #3 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> 2010-11-14 18:54:49 UTC --- I was thinking this same solution. But, maybe the user who is having the problem should just do that. In that case this is not really a bug. The problem is not knowing this is the problem. Is there a flag we can check and just not truncate at 132 or whatever length if CPP?
next prev parent reply other threads:[~2010-11-14 18:57 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-10 1:30 [Bug fortran/46405] New: " w6ws at earthlink dot net 2010-11-10 9:06 ` [Bug fortran/46405] " burnus at gcc dot gnu.org 2010-11-14 13:39 ` tkoenig at gcc dot gnu.org 2010-11-14 19:10 ` jvdelisle at gcc dot gnu.org [this message] 2010-11-14 21:12 ` burnus at gcc dot gnu.org 2010-12-16 0:14 ` dfranke at gcc dot gnu.org 2010-12-27 0:28 ` dfranke at gcc dot gnu.org 2011-01-08 23:16 ` tkoenig at gcc dot gnu.org 2011-01-08 23:35 ` 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-46405-4-ePBAhbeKoA@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).