Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Masaki Muranaka <monaka@monami-software.com>
To: gdb-patches@sourceware.org
Subject: [patch] Failed to build xstormy16-elf-gdb
Date: Mon, 22 Jan 2007 09:51:00 -0000	[thread overview]
Message-ID: <091611DC-7FB8-416F-95F0-98144362E56E@monami-software.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 277 bytes --]

Hello,

I've failed to build xstormy16-elf-gdb from CVS mainline.
Here is a fix.

2007-01-22  Masaki MURANAKA  <monaka@monami-software.com>

         * xstormy16-tdep.c (xstormy16_skip_prologue): Separate
         code from a declaration.


--
Masaki Muranaka
Monami software


[-- Attachment #2: xstormy16-tdep.c.diff --]
[-- Type: application/octet-stream, Size: 830 bytes --]

Index: xstormy16-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/xstormy16-tdep.c,v
retrieving revision 1.91
diff -u -p -r1.91 xstormy16-tdep.c
--- xstormy16-tdep.c	9 Jan 2007 17:58:59 -0000	1.91
+++ xstormy16-tdep.c	22 Jan 2007 09:47:29 -0000
@@ -416,11 +416,12 @@ xstormy16_skip_prologue (CORE_ADDR pc)
       struct symtab_and_line sal;
       struct symbol *sym;
       struct xstormy16_frame_cache cache;
+      CORE_ADDR plag_end;
 
       memset (&cache, 0, sizeof cache);
 
       /* Don't trust line number debug info in frameless functions. */
-      CORE_ADDR plg_end = xstormy16_analyze_prologue (func_addr, func_end,
+      plg_end = xstormy16_analyze_prologue (func_addr, func_end,
 						      &cache, NULL);
       if (!cache.uses_fp)
         return plg_end;

[-- Attachment #3: Type: text/plain, Size: 1 bytes --]



             reply	other threads:[~2007-01-22  9:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-22  9:51 Masaki Muranaka [this message]
2007-01-23  9:27 ` Corinna Vinschen

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=091611DC-7FB8-416F-95F0-98144362E56E@monami-software.com \
    --to=monaka@monami-software.com \
    --cc=gdb-patches@sourceware.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