public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Radek Barton <radek.barton@microsoft.com>,
	Richard Sandiford <richard.sandiford@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	"pinskia@gmail.com" <pinskia@gmail.com>,
	"10walls@gmail.com" <10walls@gmail.com>
Subject: Re: [RFC] Either fix or disable SME feature for `aarch64-w64-mingw32` target?
Date: Thu, 25 Jan 2024 17:51:38 +0000	[thread overview]
Message-ID: <ZbKfqjXXURlGjQrw@arm.com> (raw)
In-Reply-To: <PR3PR83MB0459F913A5B9DC16D1AFC166926C2@PR3PR83MB0459.EURPRD83.prod.outlook.com>

this patch added double notes on crt*.o and lse derived objects.
(which does not seem to cause build break but some linkers may
not like it)

after #include "aarch64-asm.h" all gnu-stack and gnu-property
related stuff should be removed since the header takes care of it.




  parent reply	other threads:[~2024-01-25 17:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PR3PR83MB0459E41CA2C7CF4A233A2DA492672@PR3PR83MB0459.EURPRD83.prod.outlook.com>
     [not found] ` <PR3PR83MB0459CD0B388EC092D67DCF9E92672@PR3PR83MB0459.EURPRD83.prod.outlook.com>
2024-01-04 13:50   ` Fw: " Radek Barton
2024-01-04 19:11     ` Andrew Pinski
2024-01-05 14:43       ` [EXTERNAL] " Radek Barton
2024-01-09 19:37     ` Radek Barton
2024-01-10  8:49       ` Jonathan Yong
2024-01-10  9:02         ` Iain Sandoe
2024-01-10  9:13           ` Iain Sandoe
2024-01-10 10:32             ` [EXTERNAL] " Radek Barton
2024-01-11 13:08       ` Richard Sandiford
2024-01-15 16:07         ` Radek Barton
2024-01-15 17:21           ` Radek Barton
2024-01-18 12:06             ` Radek Barton
2024-01-25 17:46             ` Szabolcs Nagy
2024-01-25 17:51             ` Szabolcs Nagy [this message]
2024-01-23 15:35           ` Richard Sandiford

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=ZbKfqjXXURlGjQrw@arm.com \
    --to=szabolcs.nagy@arm.com \
    --cc=10walls@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=pinskia@gmail.com \
    --cc=radek.barton@microsoft.com \
    --cc=richard.sandiford@arm.com \
    /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).