From: tbsaunde+gcc@tbsaunde.org
To: gcc-patches@gcc.gnu.org
Cc: Trevor Saunders <tbsaunde+gcc@tbsaunde.org>
Subject: [PATCH] fix building for alpha-dec-vms
Date: Fri, 27 Mar 2015 10:24:00 -0000 [thread overview]
Message-ID: <1427451870-16466-1-git-send-email-tbsaunde+gcc@tbsaunde.org> (raw)
From: Trevor Saunders <tbsaunde+gcc@tbsaunde.org>
Hi,
Unfortunately when testing r217869 I didn't realize the modified code in
alpha.c was only used for some alpha targets. So testing alpha-linux wasn't
enough or even really useful :(
I tested cc1 for alpha-dec-vms now builds as discussed before make all-gcc is
still broken because the vms targets don't support c++ and don't say it
shouldn't be built in config.gcc. Is this ok?
Trev
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 37258ad..fac42d6 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,9 @@
+2015-03-27 Trevor Saunders <tbsaunde@tbsaunde.org>
+
+ * config/alpha/alpha.c (alpha_use_linkage): Change type of slot to
+ alpha_links **.
+ (alpha_write_one_linkage): Correct typo.
+
2015-03-27 Marek Polacek <polacek@redhat.com>
PR sanitizer/65583
diff --git a/gcc/config/alpha/alpha.c b/gcc/config/alpha/alpha.c
index 554ff09..67c15dc 100644
--- a/gcc/config/alpha/alpha.c
+++ b/gcc/config/alpha/alpha.c
@@ -9665,7 +9665,7 @@ alpha_use_linkage (rtx func, bool lflag, bool rflag)
if (cfun->machine->links)
{
/* Is this name already defined? */
- alpha_links *slot = cfun->machine->links->get (name);
+ alpha_links **slot = cfun->machine->links->get (name);
if (slot)
al = *slot;
}
@@ -9711,7 +9711,7 @@ alpha_use_linkage (rtx func, bool lflag, bool rflag)
}
static int
-alpha_write_one_linkage (const char *name, alpha_links *link, FILE *steam)
+alpha_write_one_linkage (const char *name, alpha_links *link, FILE *stream)
{
ASM_OUTPUT_INTERNAL_LABEL (stream, XSTR (link->linkage, 0));
if (link->rkind == KIND_CODEADDR)
--
2.1.4
next reply other threads:[~2015-03-27 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 10:24 tbsaunde+gcc [this message]
2015-04-08 13:57 ` Bernhard Reutner-Fischer
2015-04-08 14:06 ` Jakub Jelinek
2015-04-08 14:03 ` Richard Biener
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=1427451870-16466-1-git-send-email-tbsaunde+gcc@tbsaunde.org \
--to=tbsaunde+gcc@tbsaunde.org \
--cc=gcc-patches@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).