From: schwab@suse.de (Andreas Schwab)
To: linux-riscv@lists.infradead.org
Subject: futex_atomic_cmpxchg_inatomic is missing
Date: Wed, 26 Sep 2018 10:41:18 +0200 [thread overview]
Message-ID: <mvmh8icabwx.fsf@suse.de> (raw)
The riscv port does not define futex_atomic_cmpxchg_inatomic, but glibc
is assuming that set_robust_list always works.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab at suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@suse.de>
To: linux-riscv@lists.infradead.org
Subject: futex_atomic_cmpxchg_inatomic is missing
Date: Wed, 26 Sep 2018 10:41:18 +0200 [thread overview]
Message-ID: <mvmh8icabwx.fsf@suse.de> (raw)
Message-ID: <20180926084118.4bUJWa6TVwLSls3Npw3BTjDZILSBSj-Hf2G4EYGM9ZA@z> (raw)
The riscv port does not define futex_atomic_cmpxchg_inatomic, but glibc
is assuming that set_robust_list always works.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2018-09-26 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 8:41 Andreas Schwab [this message]
2018-09-26 8:41 ` futex_atomic_cmpxchg_inatomic is missing Andreas Schwab
2018-09-29 2:17 ` Palmer Dabbelt
2018-09-29 2:17 ` Palmer Dabbelt
2018-10-01 7:07 ` Andreas Schwab
2018-10-01 7:07 ` Andreas Schwab
2018-10-01 22:19 ` Palmer Dabbelt
2018-10-01 22:19 ` Palmer Dabbelt
2018-10-09 16:15 ` Christoph Hellwig
2018-10-09 16:15 ` Christoph Hellwig
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=mvmh8icabwx.fsf@suse.de \
--to=schwab@suse.de \
--cc=linux-riscv@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.