ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: David Howells <dhowells@redhat.com>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Compiler shopping list
Date: Fri, 22 Jul 2016 17:52:47 +0200	[thread overview]
Message-ID: <5792414F.5040902@de.ibm.com> (raw)
In-Reply-To: <15569.1469184060@warthog.procyon.org.uk>

On 07/22/2016 12:41 PM, David Howells wrote:
> Are there additional things we can get the compiler to do for us?  Some
> things I've seen brought up:
> 
>  (1) Additional __atomic_*() ops could be useful.  Suggestions I've heard
>      include direct LL/SC support - though the compiler people don't seem so
>      keen on that.
> 
>  (2) -mmodel=kernel flag so that the compiler can optimise better for the
>      kernel memory model.

Some years ago (actually many) Linus proposed to have an endianess attribute to data
types, so that the compiler can do the bswap automatically. For some reason this
was never implemented, but this might be a good idea anyway.

e.g. 

unsigned long x[10] __attribute__(("bigendian"));

  reply	other threads:[~2016-07-22 15:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-22 10:41 David Howells
2016-07-22 15:52 ` Christian Borntraeger [this message]
2016-07-22 15:59   ` David Woodhouse
2016-07-22 17:05     ` Christian Borntraeger
2016-07-22 17:17       ` James Bottomley
2016-07-22 17:33         ` David Woodhouse
2016-07-29  1:16       ` Steven Rostedt
2016-07-23 20:35     ` Benjamin Herrenschmidt
2016-07-23 23:09       ` Alexei Starovoitov
2016-07-25 18:49 ` Luis R. Rodriguez
2016-07-29  1:32 ` Steven Rostedt

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=5792414F.5040902@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=dhowells@redhat.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    /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