From: Dominik Vogt <vogt@linux.vnet.ibm.com>
To: gcc-patches@gcc.gnu.org
Cc: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Subject: [PATCH] PR other/69006: S/390: Fix extra newlines after diagnostics.
Date: Wed, 27 Jan 2016 11:01:00 -0000 [thread overview]
Message-ID: <20160127110126.GA7243@linux.vnet.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 170 bytes --]
The attached patch removes a blank line after an error message.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69006
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
IBM Germany
[-- Attachment #2: 0001-ChangeLog --]
[-- Type: text/plain, Size: 138 bytes --]
gcc/ChangeLog
PR other/69006
* config/s390/s390-c.c (s390_resolve_overloaded_builtin): Remove
trailing blank line from error message.
[-- Attachment #3: 0001-PR-other-69006-S-390-Fix-extra-newlines-after-diagno.patch --]
[-- Type: text/x-diff, Size: 815 bytes --]
From ae4938b344821b3f6d244ec7fc5f9703599d3d55 Mon Sep 17 00:00:00 2001
From: Dominik Vogt <vogt@linux.vnet.ibm.com>
Date: Wed, 27 Jan 2016 11:50:49 +0100
Subject: [PATCH] PR other/69006: S/390: Fix extra newlines after
diagnostics.
---
gcc/config/s390/s390-c.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/config/s390/s390-c.c b/gcc/config/s390/s390-c.c
index 14d030d..2b6e405 100644
--- a/gcc/config/s390/s390-c.c
+++ b/gcc/config/s390/s390-c.c
@@ -909,7 +909,7 @@ s390_resolve_overloaded_builtin (location_t loc,
}
else if (num_matches > 1)
{
- error_at (loc, "ambiguous overload for intrinsic: %s\n",
+ error_at (loc, "ambiguous overload for intrinsic: %s",
IDENTIFIER_POINTER (DECL_NAME (ob_fndecl)));
return error_mark_node;
}
--
2.3.0
next reply other threads:[~2016-01-27 11:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 11:01 Dominik Vogt [this message]
2016-01-27 14:24 ` David Malcolm
2016-01-29 8:56 ` Dominik Vogt
2016-01-29 10:13 ` Andreas Krebbel
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=20160127110126.GA7243@linux.vnet.ibm.com \
--to=vogt@linux.vnet.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=krebbel@linux.vnet.ibm.com \
/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).