public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/737] support -mno-tls-direct-seg-refs builds
Date: Wed, 16 Feb 2005 11:08:00 -0000 [thread overview]
Message-ID: <20050216110749.11634.qmail@sourceware.org> (raw)
In-Reply-To: <20050216044437.737.roland@gnu.org>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-16 11:07 -------
Subject: Bug 737
CVSROOT: /cvs/glibc
Module name: libc
Branch: glibc-2_3-branch
Changes by: roland@sources.redhat.com 2005-02-16 11:07:22
Modified files:
sysdeps/i386 : Makefile
sysdeps/unix/i386: sysdep.S
Log message:
2005-01-23 Roland McGrath <roland@redhat.com>
[BZ #737]
* sysdeps/i386/Makefile (defines): If -mno-tls-direct-seg-refs appears
in $(CFLAGS), add -DNO_TLS_DIRECT_SEG_REFS.
* sysdeps/unix/sysv/linux/i386/sysdep.h [USE___THREAD]
(SYSCALL_ERROR_HANDLER) [NO_TLS_DIRECT_SEG_REFS]: Load thread pointer
from %gs:0 and add to that value, rather that direct %gs:OFFSET access.
* sysdeps/unix/i386/sysdep.S [NO_TLS_DIRECT_SEG_REFS]: Likewise.
Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/sysdeps/i386/Makefile.diff?cvsroot=glibc&only_with_tag=glibc-2_3-branch&r1=1.17&r2=1.17.2.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/sysdeps/unix/i386/sysdep.S.diff?cvsroot=glibc&only_with_tag=glibc-2_3-branch&r1=1.23&r2=1.23.2.1
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-16 11:07 -------
Subject: Bug 737
CVSROOT: /cvs/glibc
Module name: libc
Branch: glibc-2_3-branch
Changes by: roland@sources.redhat.com 2005-02-16 11:07:27
Modified files:
sysdeps/unix/sysv/linux/i386: sysdep.h
Log message:
2005-01-26 Jakub Jelinek <jakub@redhat.com>
[BZ #737]
* sysdeps/unix/sysv/linux/i386/sysdep.h
(SYSCALL_ERROR_HANDLER_TLS_STORE): Remove unnecessary 0 imm.
2005-01-23 Roland McGrath <roland@redhat.com>
[BZ #737]
* sysdeps/i386/Makefile (defines): If -mno-tls-direct-seg-refs appears
in $(CFLAGS), add -DNO_TLS_DIRECT_SEG_REFS.
* sysdeps/unix/sysv/linux/i386/sysdep.h [USE___THREAD]
(SYSCALL_ERROR_HANDLER) [NO_TLS_DIRECT_SEG_REFS]: Load thread pointer
from %gs:0 and add to that value, rather that direct %gs:OFFSET access.
* sysdeps/unix/i386/sysdep.S [NO_TLS_DIRECT_SEG_REFS]: Likewise.
Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/sysdeps/unix/sysv/linux/i386/sysdep.h.diff?cvsroot=glibc&only_with_tag=glibc-2_3-branch&r1=1.57&r2=1.57.2.1
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=737
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2005-02-16 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 4:44 [Bug libc/737] New: " roland at gnu dot org
2005-02-16 11:08 ` [Bug libc/737] " cvs-commit at gcc dot gnu dot org
2005-02-16 11:08 ` cvs-commit at gcc dot gnu dot org [this message]
2005-02-16 11:08 ` cvs-commit at gcc dot gnu dot org
2005-04-05 23:59 ` roland at gnu dot org
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=20050216110749.11634.qmail@sourceware.org \
--to=sourceware-bugzilla@sources.redhat.com \
--cc=glibc-bugs@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).