From: kaz Kojima <kkojima@rr.iij4u.or.jp>
To: libc-hacker@sources.redhat.com
Subject: Re: no expected errors anymore
Date: Tue, 05 Nov 2002 16:04:00 -0000 [thread overview]
Message-ID: <200211060004.gA604mO08914@r-rr.iij4u.or.jp> (raw)
In-Reply-To: Your message of "Tue, 05 Nov 2002 00:34:34 -0800" <3DC7829A.6050406@redhat.com>
Hi,
Ulrich Drepper <drepper@redhat.com> wrote:
> You shouldn't see any expected errors from the test suite anymore. So
> report any problems once again.
I've tried this on SH. The second part of the attached patch fixed
the failure of stdlib/isomac test. The first part removes some SH
TLS relocations which are now obsoleted.
Regards,
kaz
--
2002-11-06 Kaz Kojima <kkojima@rr.iij4u.or.jp>
* elf/elf.h: Remove the obsolete SH TLS relocations.
* sysdeps/sh/bits/setjmp.h (JB_SIZE): Protect with #if defined
__USE_MISC || defined _ASM.
diff -urN ORIG/libc/elf/elf.h LOCAL/libc/elf/elf.h
--- ORIG/libc/elf/elf.h Tue Oct 29 09:57:42 2002
+++ LOCAL/libc/elf/elf.h Tue Nov 5 21:47:59 2002
@@ -2211,11 +2211,6 @@
#define R_SH_TLS_DTPMOD32 149
#define R_SH_TLS_DTPOFF32 150
#define R_SH_TLS_TPOFF32 151
-#define R_SH_TLS_GD_MOV 152
-#define R_SH_TLS_LDM_MOV 153
-#define R_SH_TLS_LDO_MOV 154
-#define R_SH_TLS_IE_MOV 155
-#define R_SH_TLS_LE_MOV 156
#define R_SH_GOT32 160
#define R_SH_PLT32 161
#define R_SH_COPY 162
diff -urN ORIG/libc/sysdeps/sh/bits/setjmp.h LOCAL/libc/sysdeps/sh/bits/setjmp.h
--- ORIG/libc/sysdeps/sh/bits/setjmp.h Fri Jul 6 13:56:03 2001
+++ LOCAL/libc/sysdeps/sh/bits/setjmp.h Wed Nov 6 06:49:58 2002
@@ -42,7 +42,9 @@
} __jmp_buf[1];
#endif
+#if defined __USE_MISC || defined _ASM
#define JB_SIZE (4 * 15)
+#endif
/* Test if longjmp to JMPBUF would unwind the frame
containing a local variable at ADDRESS. */
next prev parent reply other threads:[~2002-11-06 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 0:34 Ulrich Drepper
2002-11-05 16:04 ` kaz Kojima [this message]
2002-11-05 16:08 ` Roland McGrath
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=200211060004.gA604mO08914@r-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).