public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Olivier Hainque <hainque@adacore.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: Olivier Hainque <hainque@adacore.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Check for sysconf decl on vxworks
Date: Wed, 24 May 2023 07:31:37 +0200	[thread overview]
Message-ID: <6C8BE67E-6534-4022-B8C4-19A68D327417@adacore.com> (raw)
In-Reply-To: <orcz2qqptg.fsf@lxoliva.fsfla.org>


Good for me, thanks Alex!


> On 24 May 2023, at 07:08, Alexandre Oliva <oliva@adacore.com> wrote:
> 
> 
> The sysconf function is only available in rtp mode on vxworks.  In
> kernel mode, it is not even declared, but the feature test macro in
> the testsuite doesn't notice its absence because it's a link test, and
> vxworks kernel mode uses partial linking.
> 
> This patch introduces an alternate test on vxworks targets to check
> for a declaration and for an often-used sysconf parameter.
> 
> Bootstrapped on x86_64-linux-gnu.  Also tested on ppc- and x86-vx7r2
> with gcc-12.
> 
> 
> for  gcc/testsuite/ChangeLog
> 
> 	* lib/target-supports.exp (check_effective_target_sysconf):
> 	Check for declaration and _SC_PAGESIZE on vxworks.
> ---
> gcc/testsuite/lib/target-supports.exp |   11 +++++++++++
> 1 file changed, 11 insertions(+)
> 
> diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
> index bd9f432e4a761..263ef35a2e4df 100644
> --- a/gcc/testsuite/lib/target-supports.exp
> +++ b/gcc/testsuite/lib/target-supports.exp
> @@ -1146,6 +1146,17 @@ proc check_effective_target_mmap {} {
> # Return 1 if the target supports sysconf, 0 otherwise.
> 
> proc check_effective_target_sysconf {} {
> +    # VxWorks has sysconf in rtp mode only, but our way to test can't
> +    # tell kernel mode doesn't, as we're doing partial links for
> +    # kernel modules.  We can tell by checking for a declaration, or
> +    # for some sysconf parm, because configurations that don't offer
> +    # sysconf don't have either.
> +    if { [istarget *-*-vxworks*] } {
> +	return [check_no_compiler_messages sysconfdecl assembly {
> +	    #include <unistd.h>
> +	    int f() { return sysconf(_SC_PAGESIZE); }
> +	}];
> +    }
>     return [check_function_available "sysconf"]
> }
> 
> 
> 
> -- 
> Alexandre Oliva, happy hacker                https://FSFLA.org/blogs/lxo/
>   Free Software Activist                       GNU Toolchain Engineer
> Disinformation flourishes because many people care deeply about injustice
> but very few check the facts.  Ask me about <https://stallmansupport.org>


      reply	other threads:[~2023-05-24  5:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24  5:08 Alexandre Oliva
2023-05-24  5:31 ` Olivier Hainque [this message]

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=6C8BE67E-6534-4022-B8C4-19A68D327417@adacore.com \
    --to=hainque@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=oliva@adacore.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).