public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@baylibre.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Hongtao Liu <crazylht@gmail.com>
Subject: Re: [PATCH] x86: Update PR 35513 tests
Date: Wed, 24 Jan 2024 13:23:04 +0100	[thread overview]
Message-ID: <878r4erkd3.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <20220210135515.162048-1-hjl.tools@gmail.com>

Hi!

On 2022-02-10T05:55:15-0800, "H.J. Lu via Gcc-patches" <gcc-patches@gcc.gnu.org> wrote:
> 1. Require linker with GNU_PROPERTY_1_NEEDED support for PR 35513
> run-time tests.

Moving my x86_64-pc-linux-gnu testing from an old to a newish system
(Ubuntu 20.04), I notice:

    [-PASS: g++.target/i386/pr35513-1.C  -std=gnu++98 (test for excess errors)-]
    [-PASS:-]{+UNSUPPORTED:+} g++.target/i386/pr35513-1.C  -std=gnu++98[-execution test-]

Etc.

    [-PASS: g++.target/i386/pr35513-2.C  -std=gnu++98 (test for excess errors)-]
    [-PASS:-]{+UNSUPPORTED:+} g++.target/i386/pr35513-2.C  -std=gnu++98[-execution test-]

Etc.

..., due to the 'property_1_needed' effective-target check now
diagnosing:

    /usr/bin/ld: warning: /tmp/ccFNkvfI.o: unsupported GNU_PROPERTY_TYPE (5) type: 0xb0008000

..., with:

    $ /usr/bin/ld --version | head -n 1
    GNU ld (GNU Binutils for Ubuntu) 2.34

I'm not familiar with these properties, but I wonder if really some
support has been removed (so that this indeed is now UNSUPPORTED), or if
something's wrong somewhere (so that this should still PASS).

For reference:

> --- a/gcc/testsuite/lib/target-supports.exp
> +++ b/gcc/testsuite/lib/target-supports.exp

> +proc check_effective_target_property_1_needed { } {
> +  return [check_no_compiler_messages_nocache property_1_needed executable {
> +/* Assembly code */
> +#ifdef __LP64__
> +# define __PROPERTY_ALIGN 3
> +#else
> +# define __PROPERTY_ALIGN 2
> +#endif
> +
> +	.section ".note.gnu.property", "a"
> +	.p2align __PROPERTY_ALIGN
> +	.long 1f - 0f		/* name length.  */
> +	.long 4f - 1f		/* data length.  */
> +	/* NT_GNU_PROPERTY_TYPE_0.   */
> +	.long 5			/* note type.  */
> +0:
> +	.asciz "GNU"		/* vendor name.  */
> +1:
> +	.p2align __PROPERTY_ALIGN
> +	/* GNU_PROPERTY_1_NEEDED.  */
> +	.long 0xb0008000	/* pr_type.  */
> +	.long 3f - 2f		/* pr_datasz.  */
> +2:
> +	/* GNU_PROPERTY_1_NEEDED_INDIRECT_EXTERN_ACCESS.  */
> +	.long 1
> +3:
> +	.p2align __PROPERTY_ALIGN
> +4:
> +	.text
> +	.globl main
> +main:
> +	.byte 0
> +  } ""]
> +}


Grüße
 Thomas

  parent reply	other threads:[~2024-01-24 12:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 13:55 H.J. Lu
2022-02-12  5:43 ` Hongtao Liu
2022-02-12 13:12   ` H.J. Lu
2024-01-24 12:23 ` Thomas Schwinge [this message]
2024-01-25  2:25   ` H.J. Lu

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=878r4erkd3.fsf@euler.schwinge.homeip.net \
    --to=tschwinge@baylibre.com \
    --cc=crazylht@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.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).