From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Martin Sebor <msebor@gmail.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>,
Eric Botcazou <ebotcazou@adacore.com>
Subject: Re: [PATCH] be more permissive about function alignments (PR 88208)
Date: Wed, 05 Dec 2018 16:13:00 -0000 [thread overview]
Message-ID: <yddlg546jhg.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <142d4627-9422-2c4c-1443-5db2fbc389bc@gmail.com> (Martin Sebor's message of "Wed, 5 Dec 2018 09:05:52 -0700")
Hi Martin,
>>> PS I'm not happy about duplicating the same test across all those
>>> targets. It would be much nicer to have a single test somewhere
>>> in dg.exp #include a target-specific header with macros describing
>>> the target-specific parameters.
>>
>> why so complicated? Just have a single attr-aligned.c test, restricted
>> to the target cpus it supports via dg directives and with
>> MINALIGN/MAXALIGN definitions controlled by appropriate target macros?
>
> I have done that in the past(*) but hardcoding target-specific
> assumptions into a general test didn't feel right either given
> the design of the test suite (separate target tests).
>
> [*] see the tangle of #ifdefs in gcc/testsuite/gcc.dg/attr-aligned.c
however, gcc.target, g++.target are only meant for tests that only make
sense on a particular target and cannot work elsewhere. The current
amount of duplication between the various gcc.target/*/attr-aligned.c
tests (where the only variation I could see are the MINALIGN/MAXALIGN
definitions) seems way worse. For someone adapting the test to his
target, it's way easier to skim through the variations (hopefully with
appropriate comments where non-obvious) in a single file rather than
looking at many almost identical files in gcc.target.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
prev parent reply other threads:[~2018-12-05 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 4:33 Martin Sebor
2018-11-29 3:48 ` Jeff Law
2018-12-05 13:09 ` Rainer Orth
2018-12-05 13:50 ` Jeff Law
2018-12-05 16:05 ` Martin Sebor
2018-12-05 16:13 ` Rainer Orth [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=yddlg546jhg.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@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).