From: Kaz Kojima <kkojima@rr.iij4u.or.jp>
To: libc-hacker@sources.redhat.com
Subject: [PATCH] SH tiny tweak
Date: Tue, 31 Jan 2006 14:30:00 -0000 [thread overview]
Message-ID: <20060131.233010.93478310.kkojima@rr.iij4u.or.jp> (raw)
Hi,
On SH, I've found an error when compiling nptl/tst-cancel24 with
the C++ compiler:
../include/setjmp.h:8: error: non-local function `void __longjmp(<anonymous struct>*, int)' uses anonymous type
but missed to send the attached patch to fix it.
Regards,
kaz
--
2006-01-31 Kaz Kojima <kkojima@rr.iij4u.or.jp>
* sysdeps/sh/bits/setjmp.h: Use the structure with tag.
diff -uprN ORIG/libc/sysdeps/sh/bits/setjmp.h LOCAL/libc/sysdeps/sh/bits/setjmp.h
--- ORIG/libc/sysdeps/sh/bits/setjmp.h 2006-01-19 08:45:42.000000000 +0900
+++ LOCAL/libc/sysdeps/sh/bits/setjmp.h 2006-01-31 14:30:59.000000000 +0900
@@ -25,7 +25,7 @@
#endif
#ifndef _ASM
-typedef struct
+typedef struct __jmp_buf_s
{
/* Callee-saved registers r8 through r15. */
int __regs[8];
next reply other threads:[~2006-01-31 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 14:30 Kaz Kojima [this message]
2006-02-02 9:42 ` Roland McGrath
2006-02-02 12:26 ` Kaz Kojima
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=20060131.233010.93478310.kkojima@rr.iij4u.or.jp \
--to=kkojima@rr.iij4u.or.jp \
--cc=libc-hacker@sources.redhat.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).