From: Andreas Schwab <schwab@linux-m68k.org>
To: "Uecker\, Martin" <Martin.Uecker@med.uni-goettingen.de>
Cc: "msebor\@gmail.com" <msebor@gmail.com>,
"law\@redhat.com" <law@redhat.com>,
"joseph\@codesourcery.com" <joseph@codesourcery.com>,
"gcc-patches\@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"ebotcazou\@adacore.com" <ebotcazou@adacore.com>,
"Wilco.Dijkstra\@arm.com" <Wilco.Dijkstra@arm.com>
Subject: Re: [PATCH v4][C][ADA] use function descriptors instead of trampolines in C
Date: Mon, 17 Dec 2018 18:41:00 -0000 [thread overview]
Message-ID: <87efagro6a.fsf@igel.home> (raw)
In-Reply-To: <1545070031.3328.1.camel@med.uni-goettingen.de> (Martin Uecker's message of "Mon, 17 Dec 2018 18:07:10 +0000")
On Dez 17 2018, "Uecker, Martin" <Martin.Uecker@med.uni-goettingen.de> wrote:
> Am Montag, den 17.12.2018, 10:28 -0700 schrieb Jeff Law:
>> On 12/16/18 3:45 PM, Uecker, Martin wrote:
>> > But most architectures require a higher alignment anyway.
>> > Here is a list of all targets where function alignment
>> > is 1 byte:
>> >
>> > gcc/config/avr/avr.h:#define FUNCTION_BOUNDARY 8
>> > gcc/config/i386/i386.h:#define FUNCTION_BOUNDARY 8
>> > gcc/config/m32c/m32c.h:#define FUNCTION_BOUNDARY 8
>> > gcc/config/mn10300/mn10300.h:#define FUNCTION_BOUNDARY 8
>> > gcc/config/pa/pa.h:#define FUNCTION_BOUNDARY BITS_PER_WORD
>> > gcc/config/rl78/rl78.h:#define FUNCTION_BOUNDARYÂ 8
>> > gcc/config/rx/rx.h:#define FUNCTION_BOUNDARYÂ ((rx_cpu_type == RX100 ||
>> > rx_cpu_type == RX200) ? 4 : 8)
>
> (BTW: pa was included here by mistake)
The rx config apparently confused bits and bytes.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2018-12-17 18:41 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-11 16:41 [RFC] [PATCH][C][ADA] " Uecker, Martin
2018-08-18 16:33 ` Uecker, Martin
2018-08-20 14:07 ` [PATCH v2][C][ADA] " Uecker, Martin
2018-08-20 22:35 ` Joseph Myers
2018-08-21 6:17 ` Uecker, Martin
2018-08-21 21:34 ` Joseph Myers
2018-08-22 6:09 ` Uecker, Martin
2018-08-22 15:49 ` Joseph Myers
2018-11-04 20:49 ` [PATCH v3][C][ADA] " Uecker, Martin
2018-12-03 10:29 ` Uecker, Martin
2018-12-03 21:56 ` Jeff Law
2018-12-12 18:12 ` [PATCH v4][C][ADA] " Uecker, Martin
2018-12-13 23:35 ` Jeff Law
2018-12-14 10:05 ` Uecker, Martin
2018-12-14 23:36 ` Jeff Law
2018-12-15 1:20 ` Martin Sebor
2018-12-16 13:46 ` Uecker, Martin
2018-12-16 16:13 ` Jeff Law
2018-12-16 22:46 ` Uecker, Martin
2018-12-17 15:26 ` Szabolcs Nagy
2018-12-17 18:22 ` Uecker, Martin
2018-12-17 19:24 ` Szabolcs Nagy
2018-12-18 15:23 ` Paul Koning
2018-12-18 15:32 ` Jakub Jelinek
2018-12-18 16:03 ` Jeff Law
2018-12-18 16:25 ` Jakub Jelinek
2018-12-18 16:29 ` Uecker, Martin
2018-12-18 16:33 ` Uecker, Martin
2018-12-18 16:42 ` Jakub Jelinek
2018-12-19 19:53 ` Uecker, Martin
2018-12-19 20:08 ` Jakub Jelinek
2018-12-19 21:28 ` Wilco Dijkstra
2018-12-21 21:41 ` Hans-Peter Nilsson
2018-12-21 22:07 ` Uecker, Martin
2018-12-20 13:29 ` Wilco Dijkstra
2018-12-18 16:27 ` Uecker, Martin
2018-12-17 17:29 ` Jeff Law
2018-12-17 18:07 ` Uecker, Martin
2018-12-17 18:41 ` Andreas Schwab [this message]
2018-12-21 8:03 ` [PATCH v5][C][ADA] " Uecker, Martin
2019-01-13 21:19 ` [PING] " Uecker, Martin
2019-01-14 20:16 ` Jeff Law
2019-06-24 21:35 ` [PATCH v6][C][ADA] " Uecker, Martin
2019-08-09 23:42 ` Jeff Law
2019-08-10 10:16 ` Uecker, Martin
2018-12-19 19:11 ` [PATCH v4][C][ADA] " Uecker, Martin
2018-12-17 17:31 ` Martin Sebor
2018-12-17 18:09 ` Uecker, Martin
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=87efagro6a.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=Martin.Uecker@med.uni-goettingen.de \
--cc=Wilco.Dijkstra@arm.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=law@redhat.com \
--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).