From: Zack Weinberg <zackw@panix.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Florian Weimer <fweimer@redhat.com>,
Joseph Myers <joseph@codesourcery.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Fix location where math-vector-fortran.h is installed.
Date: Wed, 27 Feb 2019 10:00:57 -0500 [thread overview]
Message-ID: <CAKCAbMhv6wVpZrLTziv+98FSquofh5pmoLQ=A7M40+57Fd1P1Q@mail.gmail.com> (raw)
In-Reply-To: <e1bdc055-e8a8-d3a9-794e-1f722bc82f1e@suse.cz>
On Wed, Feb 27, 2019 at 3:09 AM Martin Liška <mliska@suse.cz> wrote:
> On 2/26/19 10:41 PM, Zack Weinberg wrote:
> > On Tue, Feb 26, 2019 at 4:16 PM Florian Weimer <fweimer@redhat.com> wrote:
> >> * Martin Liška:
> >>> On 2/26/19 7:05 PM, Joseph Myers wrote:
> >>>> On Tue, 26 Feb 2019, Martin Liška wrote:
> >>>>
> >>>>> Hi.
> >>>>>
> >>>>> This is follow up patch where I fix location where the header
> >>>>> is installed. I made a type as I was copying & pasting.
> >
> > Do I understand correctly that the desired installation location is
> > $(prefix)/include/finclude/math-vector-fortran.h ?
>
> Yes.
Will there ever be C headers in $(prefix)/include/finclude ?
> >> In file included from /tmp/cih_test_C67G81.c:8:
> >> ../sysdeps/x86/fpu/finclude/math-vector-fortran.h:1:1: error: expected identifie
> >> r or ‘(’ before ‘!’ token
> >> ! Platform-specific declarations of SIMD math functions for Fortran. -*- f90 -*
>
> I skipped that header explicitly.
...
> + # Skip Fortran header
> + (finclude/math-vector-fortran.h)
> + continue;;
To put the above question another way, is there a reason why this shouldn't be
+ # Skip Fortran headers
+ (finclude/*)
+ continue;;
?
> And for the check-wrapper-headers.py, I read a header file and skip files
> with 'f90' file type.
If you're going to do it this way, I recommend you copy the more
general Emacs modeline parser from
https://sourceware.org/ml/libc-alpha/2019-02/msg00539.html ... but if
we can just skip finclude/* that might be a better approach for both
scripts.
zw
next prev parent reply other threads:[~2019-02-27 15:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 14:31 [PATCH] Add new Fortran vector math header file Martin Liška
2019-02-18 17:55 ` Joseph Myers
2019-02-19 9:18 ` Martin Liška
2019-02-19 17:59 ` Joseph Myers
2019-02-19 19:14 ` Zack Weinberg
2019-02-20 9:43 ` Martin Liška
2019-02-20 13:05 ` Zack Weinberg
2019-02-20 13:52 ` Martin Liška
2019-02-26 17:56 ` [PATCH] Fix location where math-vector-fortran.h is installed Martin Liška
2019-02-26 18:05 ` Joseph Myers
2019-02-26 18:30 ` Martin Liška
2019-02-26 21:16 ` Florian Weimer
2019-02-26 21:41 ` Zack Weinberg
2019-02-27 8:09 ` Martin Liška
2019-02-27 10:12 ` Florian Weimer
2019-02-27 10:36 ` Martin Liška
2019-02-27 11:30 ` Andreas Schwab
2019-02-27 11:53 ` Martin Liška
2019-02-27 15:00 ` Zack Weinberg [this message]
2019-02-28 13:18 ` Martin Liška
2019-02-28 13:30 ` Zack Weinberg
2019-02-28 13:32 ` Florian Weimer
2019-03-01 9:31 ` Martin Liška
2019-03-01 22:30 ` Steve Ellcey
2019-03-05 12:03 ` Martin Liška
2019-03-06 21:13 ` Joseph Myers
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKCAbMhv6wVpZrLTziv+98FSquofh5pmoLQ=A7M40+57Fd1P1Q@mail.gmail.com' \
--to=zackw@panix.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=mliska@suse.cz \
/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).