public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/105413] gdc extended assembler cannot constraints r8 - r15
Date: Fri, 24 Jun 2022 18:55:35 +0000	[thread overview]
Message-ID: <bug-105413-4-z19gZePx0X@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105413-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105413

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Iain Buclaw <ibuclaw@gcc.gnu.org>:

https://gcc.gnu.org/g:91418c42089cd1cbe71edcd6b2f5b26559819372

commit r13-1255-g91418c42089cd1cbe71edcd6b2f5b26559819372
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date:   Thu Jun 23 18:24:07 2022 +0200

    d: Add `@register' attribute to compiler and library.

    The `@register` attribute specifies that a local or `__gshared` variable
    is to be given a register storage-class in the C sense of the term, and
    will be placed into a register named `registerName`.

    The variable needs to boiled down to a data type that fits the target
    register.  It also cannot have either thread-local or `extern` storage.
    It is an error to take the address of a register variable.

            PR d/105413

    gcc/d/ChangeLog:

            * d-attribs.cc (d_handle_register_attribute): New function.
            (d_langhook_attribute_table): Add register attribute.
            * d-codegen.cc (d_mark_addressable): Error if taken address of
            register variable.
            (build_frame_type): Error if register variable has non-local
            references.
            * d-tree.h (d_mark_addressable): Add complain parameter.
            * decl.cc (get_symbol_decl): Mark register varibles DECL_REGISTER.
            Error when register variable declared thread-local or extern.
            * expr.cc (ExprVisitor::visit (IndexExp *)): Don't complain about
            marking register vectors as addressable in an ARRAY_REF.

    libphobos/ChangeLog:

            * libdruntime/gcc/attributes.d (register): Define.

    gcc/testsuite/ChangeLog:

            * gdc.dg/attr_register1.d: New test.
            * gdc.dg/attr_register2.d: New test.
            * gdc.dg/attr_register3.d: New test.

  reply	other threads:[~2022-06-24 18:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 23:13 [Bug d/105413] New: " witold.baryluk+gcc at gmail dot com
2022-06-24 18:55 ` cvs-commit at gcc dot gnu.org [this message]
2022-06-24 19:19 ` [Bug d/105413] " ibuclaw at gdcproject dot org
2022-10-08 20:08 ` witold.baryluk+gcc at gmail 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-105413-4-z19gZePx0X@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).