public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Dmitry Fleytman <dmitry.fleytman@gmail.com>,
	sheepdog@lists.wpkg.org,
	Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>,
	Li Zhijian <lizhijian@cn.fujitsu.com>,
	David Hildenbrand <david@redhat.com>,
	Jason Wang <jasowang@redhat.com>,
	Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>,
	BALATON Zoltan <balaton@eik.bme.hu>,
	Keith Busch <keith.busch@intel.com>,
	Max Filippov <jcmvbkbc@gmail.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	Max Reitz <mreitz@redhat.com>, Yongbok Kim <yongbok.kim@mips.com>,
	Hannes Reinecke <hare@suse.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	zhanghailiang <zhang.zhanghailiang@huawei.com>,
	Ben Warren <ben@skyportsystems.com>,
	Stefan Berger <stefanb@linux.vnet.ibm.com>,
	Ronnie Sahlberg <ronniesahlberg@gmail.com>,
Subject: Re: [Qemu-block] [PATCH] qemu: include generated files with <> and not ""
Date: Tue, 20 Mar 2018 15:30:15 +0200	[thread overview]
Message-ID: <20180320152446-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20180320131041.GB24329@stefanha-x1.localdomain>

On Tue, Mar 20, 2018 at 01:10:41PM +0000, Stefan Hajnoczi wrote:
> On Tue, Mar 20, 2018 at 03:54:36AM +0200, Michael S. Tsirkin wrote:
> > QEMU coding style at the moment asks for all non-system
> > include files to be used with #include "foo.h".
> > However this rule actually does not make sense and
> > creates issues for when the included file is generated.
> > 
> > In C, include "file" means look in current directory,
> > then on include search path. Current directory here
> > means the source file directory.
> > By comparison include <file> means look on include search path.
> > 
> > As generated files are not in the search directory (unless the build
> > directory happens to match the source directory), it does not make sense
> > to include them with "" - doing so is merely more work for preprocessor
> > and a source or errors if a stale file happens to exist in the source
> > directory.
> > 
> > This changes include directives for all generated files, across the
> > tree. The idea is to avoid sending a huge amount of email.  But when
> > merging, the changes will be split with one commit per file, e.g. for
> > ease of bisect in case of build failures, and to ease merging.
> > 
> > Note that should some generated files be missed by this tree-wide
> > refactoring, it isn't a big deal - this merely maintains the status quo,
> > and this can be addressed by a separate patch on top.
> 
> Stale header files are a pain.  I often do make distclean before
> checking out a radically different QEMU version to avoid the problem.
> 
> This patch trades off the stale header file issue for a new approach to
> using <> vs "", which will be hard to use consistently

The proposed rule is to use <> everywhere except if the file is in the
source directory.  It will be very easy to use consistently for the
simple reason that compiler will enforce it.  If you use <> for a header
in the current directory build fails. So you are forced to use "".

> in the future
> since it is unconventional.

All compilers I know without exception implement
include <> meaning look in -I search path, and
include "" meaning look in current directory then
in -I search path.

Looks conventional to me.

> Is the build time improvement worth it (please post numbers)?
> 
> Stefan

Haven't tested it frankly. Will it convince anyone if it's marginally
faster?

-- 
MST

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-03-20 13:30 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20  1:54 [PATCH] qemu: include generated files with <> and not "" Michael S. Tsirkin
2018-03-20  8:58 ` Laurent Vivier
2018-03-20  9:44   ` Daniel P. Berrangé
2018-03-20 10:01     ` Peter Maydell
2018-03-20 10:27       ` Daniel P. Berrangé
2018-03-20 11:52         ` Michael S. Tsirkin
2018-03-20 12:12     ` Michael S. Tsirkin
2018-03-20 12:18       ` Daniel P. Berrangé
2018-03-20 12:28         ` Michael S. Tsirkin
2018-03-20 12:39           ` Daniel P. Berrangé
2018-03-20 12:44             ` Michael S. Tsirkin
2018-03-20 13:32             ` Gerd Hoffmann
2018-03-20 13:41               ` Daniel P. Berrangé
2018-03-20 13:50                 ` Michael S. Tsirkin
2018-03-20 13:58                   ` Daniel P. Berrangé
2018-03-20 14:02                     ` Michael S. Tsirkin
2018-03-20 13:54                 ` Max Reitz
2018-03-20 17:12                   ` Michael S. Tsirkin
2018-03-20 13:46               ` Thomas Huth
2018-03-20 13:53                 ` Michael S. Tsirkin
2018-03-20 12:05   ` Michael S. Tsirkin
2018-03-21  7:16     ` [Qemu-ppc] " Thomas Huth
2018-03-21 13:08       ` Michael S. Tsirkin
2018-03-21 13:15         ` Stefan Weil
2018-03-21 13:24           ` Michael S. Tsirkin
2018-03-21 13:29         ` Daniel P. Berrangé
2018-03-21 13:42           ` Michael S. Tsirkin
2018-03-20 13:05 ` Michael S. Tsirkin
2018-03-20 13:10 ` [Qemu-block] " Stefan Hajnoczi
2018-03-20 13:30   ` Michael S. Tsirkin [this message]
2018-03-20 16:12 ` Eric Blake
2018-03-20 16:40   ` Daniel P. Berrangé
2018-03-20 16:51   ` Michael S. Tsirkin
2018-03-20 16:33 ` [Qemu-devel] " Stefan Weil
2018-03-20 17:10   ` Michael S. Tsirkin
2018-03-20 17:34     ` Daniel P. Berrangé
2018-03-20 17:49       ` Michael S. Tsirkin
2018-03-20 17:36   ` Daniel P. Berrangé

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=20180320152446-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=agraf@suse.de \
    --cc=balaton@eik.bme.hu \
    --cc=ben@skyportsystems.com \
    --cc=david@redhat.com \
    --cc=dmitry.fleytman@gmail.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=hare@suse.com \
    --cc=jasowang@redhat.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=keith.busch@intel.com \
    --cc=kraxel@redhat.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=mreitz@redhat.com \
    --cc=pavel.dovgaluk@ispras.ru \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=ronniesahlberg@gmail.com \
    --cc=sheepdog@lists.wpkg.org \
    --cc=sstabellini@kernel.org \
    --cc=stefanb@linux.vnet.ibm.com \
    --cc=stefanha@gmail.com \
    --cc=yongbok.kim@mips.com \
    --cc=zhang.zhanghailiang@huawei.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