All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javi Merino <javi.merino@cloud.com>
To: xen-devel@lists.xenproject.org
Cc: Javi Merino <javi.merino@cloud.com>,
	Jan Beulich <jbeulich@suse.com>, Henry Wang <Henry.Wang@arm.com>
Subject: [XEN PATCH v2 0/2] update gcov info for newer versions of gcc
Date: Fri,  8 Sep 2023 17:20:30 +0100	[thread overview]
Message-ID: <cover.1694189143.git.javi.merino@cloud.com> (raw)

The gcov info changes with different versions of gcc.  This patch
series updates it so that we can capture coverage for xen built with
newer compilers.

This doesn't solve all the problems with coverage as Xen still crashes
when trying to reset/read coverage[0].  Still, it's a step forward.

[0] https://gitlab.com/xen-project/xen/-/issues/168

I have tested it with a workaround for the aforementioned bug
(commenting out freeing of the init sections) and the following gcc
versions:
  - gcc 4.8.5
  - gcc 4.9.4
  - gcc 6.5.0
  - gcc 7.5.0
  - gcc 8.5.0
  - gcc 9.5.0
  - gcc 10.5.0
  - gcc 11.4.0
  - gcc 12.3.0

Javi Merino (2):
  coverage: simplify the logic of choosing the number of gcov counters
    depending on the gcc version
  coverage: update gcov info for newer versions of gcc

 xen/common/coverage/Makefile  |  6 +-----
 xen/common/coverage/gcc_4_7.c | 39 ++++++++++++++++++++++++++---------
 xen/common/coverage/gcc_4_9.c | 33 -----------------------------
 xen/common/coverage/gcc_5.c   | 33 -----------------------------
 xen/common/coverage/gcc_7.c   | 30 ---------------------------
 5 files changed, 30 insertions(+), 111 deletions(-)
 delete mode 100644 xen/common/coverage/gcc_4_9.c
 delete mode 100644 xen/common/coverage/gcc_5.c
 delete mode 100644 xen/common/coverage/gcc_7.c

-- 
2.41.0



             reply	other threads:[~2023-09-08 16:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08 16:20 Javi Merino [this message]
2023-09-08 16:20 ` [XEN PATCH v2 1/2] coverage: simplify the logic of choosing the number of gcov counters depending on the gcc version Javi Merino
2023-09-11  7:54   ` Jan Beulich
2023-09-11  9:13     ` Javi Merino
2023-09-11  9:48     ` Andrew Cooper
2023-09-11  9:53       ` Jan Beulich
2023-09-11  9:59         ` Andrew Cooper
2023-09-11 10:33           ` Jan Beulich
2023-09-08 16:20 ` [XEN PATCH v2 2/2] coverage: update gcov info for newer versions of gcc Javi Merino
2023-09-11  8:00   ` Jan Beulich
2023-09-11  9:19     ` Javi Merino

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=cover.1694189143.git.javi.merino@cloud.com \
    --to=javi.merino@cloud.com \
    --cc=Henry.Wang@arm.com \
    --cc=jbeulich@suse.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.