public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Ondřej Bílka" <neleai@seznam.cz> To: bugdal at aerifal dot cx <sourceware-bugzilla@sourceware.org> Cc: glibc-bugs@sourceware.org Subject: Re: [Bug dynamic-link/15128] dynamic loader may clobber floating-point parameters on AArch64 Date: Mon, 11 Feb 2013 07:21:00 -0000 [thread overview] Message-ID: <20130211071202.GA5915@domone> (raw) In-Reply-To: <bug-15128-131-YWrDFrBQkz@http.sourceware.org/bugzilla/> On Mon, Feb 11, 2013 at 05:00:30AM +0000, bugdal at aerifal dot cx wrote: > http://sourceware.org/bugzilla/show_bug.cgi?id=15128 > > Rich Felker <bugdal at aerifal dot cx> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |bugdal at aerifal dot cx > > --- Comment #1 from Rich Felker <bugdal at aerifal dot cx> 2013-02-11 05:00:30 UTC --- > I haven't looked at the code, but the correct fix should just be to make the > lazy binding resolver function save all registers that might be argument > registers before calling anything else, and restore them before making the > final jump to the resolved address. There's no reason to go to great lengths to > avoid clobbering them in between. > Aarch64 ta calling conventions below you have v16-v31 available. The first eight registers, v0-v7, are used to pass argument values into a subroutine and to return result values from a function. They may also be used to hold intermediate values within a routine (but, in general, only between subroutine calls). Registers d8-d15 (s8-s15) must be preserved by a callee across subroutine calls; the remaining registers (v0-v7, v16-v31) do not need to be preserved (or should be preserved by the caller). Additionally, only single-precision, double-precision and 64-bit short vector values stored in d8-d15 (s8-s15) need to be preserved; it is the responsibility of the caller to preserve larger values. > -- > Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug.
next prev parent reply other threads:[~2013-02-11 7:21 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-09 17:03 [Bug dynamic-link/15128] New: " mikpe at it dot uu.se 2013-02-09 17:04 ` [Bug dynamic-link/15128] " mikpe at it dot uu.se 2013-02-11 5:00 ` bugdal at aerifal dot cx 2013-02-11 7:21 ` Ondřej Bílka [this message] 2013-02-11 7:21 ` neleai at seznam dot cz 2013-02-11 9:09 ` mikpe at it dot uu.se 2013-02-11 13:36 ` bugdal at aerifal dot cx 2013-02-11 15:13 ` mikpe at it dot uu.se 2013-02-11 21:38 ` bugdal at aerifal dot cx 2013-02-13 9:32 ` mikpe at it dot uu.se 2013-02-20 18:12 ` carlos at redhat dot com 2013-02-24 18:11 ` amonakov at gmail dot com 2013-02-24 18:13 ` amonakov at gmail dot com 2013-02-25 8:06 ` aj at suse dot de 2013-05-21 12:59 ` marcus.shawcroft at linaro dot org 2013-10-02 22:15 ` neleai at seznam dot cz 2013-12-18 12:08 ` cvs-commit at gcc dot gnu.org 2013-12-19 14:04 ` cvs-commit at gcc dot gnu.org 2013-12-19 14:10 ` marcus.shawcroft at linaro dot org 2014-06-13 18:52 ` fweimer at redhat dot com 2015-07-31 12:33 ` cvs-commit at gcc dot gnu.org 2015-08-01 15:55 ` cvs-commit at gcc dot gnu.org 2015-08-01 22:23 ` cvs-commit at gcc dot gnu.org 2015-08-01 22:25 ` cvs-commit at gcc dot gnu.org 2015-08-02 3:55 ` cvs-commit at gcc dot gnu.org 2015-08-02 12:33 ` cvs-commit at gcc dot gnu.org 2015-08-02 13:57 ` cvs-commit at gcc dot gnu.org 2015-08-02 17:41 ` cvs-commit at gcc dot gnu.org 2015-08-02 17:43 ` cvs-commit at gcc dot gnu.org 2015-08-03 4:47 ` cvs-commit at gcc dot gnu.org 2015-08-03 4:50 ` cvs-commit at gcc dot gnu.org 2015-08-03 17:21 ` cvs-commit at gcc dot gnu.org 2015-08-03 19:32 ` cvs-commit at gcc dot gnu.org 2015-08-03 21:25 ` cvs-commit at gcc dot gnu.org 2015-08-03 21:36 ` cvs-commit at gcc dot gnu.org 2015-08-05 14:34 ` cvs-commit at gcc dot gnu.org 2015-08-05 14:35 ` cvs-commit at gcc dot gnu.org 2015-08-07 22:45 ` jsweval at arxan dot com 2015-08-19 12:19 ` cvs-commit at gcc dot gnu.org 2015-08-24 13:19 ` cvs-commit at gcc dot gnu.org 2015-08-25 11:31 ` cvs-commit at gcc dot gnu.org 2015-08-25 11:53 ` cvs-commit at gcc dot gnu.org 2023-12-08 9:28 ` liqingqing3 at huawei dot com 2023-12-08 10:37 ` fweimer at redhat dot com
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=20130211071202.GA5915@domone \ --to=neleai@seznam.cz \ --cc=glibc-bugs@sourceware.org \ --cc=sourceware-bugzilla@sourceware.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: linkBe 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).