From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-patches:master commit in: 3.4.6/gentoo/
Date: Fri, 30 Nov 2018 07:37:26 +0000 (UTC) [thread overview]
Message-ID: <1543563434.5cf1ca6fe141211691f0c762f139d80e591a5b71.slyfox@gentoo> (raw)
commit: 5cf1ca6fe141211691f0c762f139d80e591a5b71
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Fri Nov 30 07:36:34 2018 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Fri Nov 30 07:37:14 2018 +0000
URL: https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=5cf1ca6f
3.4.6: update 91_all_ucontext-to-ucontext_t for libjava
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
3.4.6/gentoo/91_all_ucontext-to-ucontext_t.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/3.4.6/gentoo/91_all_ucontext-to-ucontext_t.patch b/3.4.6/gentoo/91_all_ucontext-to-ucontext_t.patch
index 0ce1ed4..f927cff 100644
--- a/3.4.6/gentoo/91_all_ucontext-to-ucontext_t.patch
+++ b/3.4.6/gentoo/91_all_ucontext-to-ucontext_t.patch
@@ -60,7 +60,7 @@ https://bugs.gentoo.org/664486
instruction: the x86_64 exception handler expects \
the PC to point to the instruction after a call. */ \
- struct ucontext *_uc = (struct ucontext *)_p; \
-+ ucontext_t *_uc = (struct ucontext *)_p; \
++ ucontext_t *_uc = (ucontext_t *)_p; \
volatile struct sigcontext *_sc = (struct sigcontext *) &_uc->uc_mcontext; \
_sc->rip += 2; \
} \
next reply other threads:[~2018-11-30 7:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 7:37 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-27 19:45 [gentoo-commits] proj/gcc-patches:master commit in: 3.4.6/gentoo/ Sergei Trofimovich
2019-10-21 22:16 Sergei Trofimovich
2019-06-15 19:11 Sergei Trofimovich
2019-06-15 19:01 Sergei Trofimovich
2019-06-12 21:30 Sergei Trofimovich
2019-06-01 10:01 Sergei Trofimovich
2018-09-30 12:27 Sergei Trofimovich
2018-09-29 20:31 Sergei Trofimovich
2018-09-16 16:10 Sergei Trofimovich
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=1543563434.5cf1ca6fe141211691f0c762f139d80e591a5b71.slyfox@gentoo \
--to=slyfox@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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