public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "scox at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/28334] cannot handle offset into register
Date: Thu, 19 May 2022 20:25:37 +0000	[thread overview]
Message-ID: <bug-28334-6586-T88AkVVUpv@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28334-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28334

Stan Cox <scox at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |scox at redhat dot com
         Resolution|---                         |FIXED

--- Comment #1 from Stan Cox <scox at redhat dot com> ---
This is due to the x8664 abi which specifies how structures are passed.  The
structure in the example is returned by value, which will return the struct
members in successive registers as specified by the x8664 abi.  In this
particular case members are packed into a single register and systemtap is thus
not able to pry it apart.  Thus the error "cannot handle offset into register"

The abi says:
 The classification of aggregate (structures and arrays) and union types works
as follows:
1. If the size of an object is larger than four eightbytes, or it contains
unaligned
fields, it has class MEMORY

So if the example is changed to be double width; double angle; then the abi
threshold is hit, the struct is passed by reference and systemtap can then
access individual members.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  reply	other threads:[~2022-05-19 20:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 10:20 [Bug translator/28334] New: " 913495245 at qq dot com
2022-05-19 20:25 ` scox at redhat dot com [this message]
2022-05-19 20:31 ` [Bug translator/28334] " fche at redhat dot com
2022-05-19 20:50 ` scox at redhat dot com
2022-07-01 17:39 ` wcohen at redhat dot com
2022-07-01 17:44 ` wcohen 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=bug-28334-6586-T88AkVVUpv@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@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: 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).