From: Ian Lance Taylor <iant@google.com>
To: gcc-patches@gcc.gnu.org
Subject: [gcc-in-cxx] Fix builtins.c for C++
Date: Wed, 02 Jul 2008 05:47:00 -0000 [thread overview]
Message-ID: <m3r6ackfh0.fsf@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 278 bytes --]
I committed this patch to the gcc-in-cxx branch to fix builtins.c for
C++.
Ian
2008-07-01 Ian Lance Taylor <iant@google.com>
* builtins.c (expand_builtin_profile_func): Rename local variable
this to this_func.
(validate_arglist): Pass int rather than enum to va_arg.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Fix builtins.c for C++ --]
[-- Type: text/x-patch, Size: 1088 bytes --]
Index: builtins.c
===================================================================
--- builtins.c (revision 137267)
+++ builtins.c (working copy)
@@ -5513,18 +5513,18 @@ expand_builtin_sprintf (tree exp, rtx ta
static rtx
expand_builtin_profile_func (bool exitp)
{
- rtx this, which;
+ rtx this_func, which;
- this = DECL_RTL (current_function_decl);
- gcc_assert (MEM_P (this));
- this = XEXP (this, 0);
+ this_func = DECL_RTL (current_function_decl);
+ gcc_assert (MEM_P (this_func));
+ this_func = XEXP (this_func, 0);
if (exitp)
which = profile_function_exit_libfunc;
else
which = profile_function_entry_libfunc;
- emit_library_call (which, LCT_NORMAL, VOIDmode, 2, this, Pmode,
+ emit_library_call (which, LCT_NORMAL, VOIDmode, 2, this_func, Pmode,
expand_builtin_return_addr (BUILT_IN_RETURN_ADDRESS,
0),
Pmode);
@@ -10810,7 +10810,7 @@ validate_arglist (const_tree callexpr, .
do
{
- code = va_arg (ap, enum tree_code);
+ code = (enum tree_code) va_arg (ap, int);
switch (code)
{
case 0:
reply other threads:[~2008-07-02 5:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3r6ackfh0.fsf@google.com \
--to=iant@google.com \
--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).