public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/97390] Error compiling acc data present
Date: Tue, 13 Oct 2020 08:11:47 +0000 [thread overview]
Message-ID: <bug-97390-4-Rg2FNFCeP9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97390-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97390
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
CC| |burnus at gcc dot gnu.org,
| |tschwinge at gcc dot gnu.org
Last reconfirmed| |2020-10-13
Status|UNCONFIRMED |WAITING
Assignee|unassigned at gcc dot gnu.org |tschwinge at gcc dot gnu.org
--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Would it be the case that this line is longer than 132 characters? After this,
"characters are ignored in typical free-form lines in the source file"; see the
'-ffree-line-length' option. Thus, does '-ffree-line-length-none' help?
(I cannot comment on (a) why that's a useful limit to have, and (b) whether the
error reporting shouldn't be improved.)
next prev parent reply other threads:[~2020-10-13 8:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 20:16 [Bug fortran/97390] New: " afernandez at odyhpc dot com
2020-10-13 8:11 ` tschwinge at gcc dot gnu.org [this message]
2020-10-13 13:56 ` [Bug fortran/97390] " afernandez at odyhpc dot com
2020-10-13 14:48 ` tschwinge at gcc dot gnu.org
2020-10-13 15:38 ` afernandez at odyhpc dot com
2020-10-13 17:33 ` [Bug fortran/97390] [OpenAError " burnus at gcc dot gnu.org
2020-10-13 21:55 ` [Bug fortran/97390] [OpenACC] Error " afernandez at odyhpc dot com
2020-10-14 8:34 ` [Bug fortran/97390] [OpenACC] 'async' clause on 'data' construct tschwinge at gcc dot gnu.org
2020-10-14 13:53 ` cvs-commit at gcc dot gnu.org
2022-01-11 16:31 ` tschwinge 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-97390-4-Rg2FNFCeP9@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: link
Be 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).