public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Jambor <mjambor@suse.cz>
To: GCC Mailing List <gcc@gcc.gnu.org>
Cc: Roger Sayle <roger@nextmovesoftware.com>
Subject: Issue generating GCC coverage report since r14-1625-geba3565ce6d766
Date: Fri, 16 Jun 2023 14:51:24 +0200	[thread overview]
Message-ID: <ri6edmb4lkj.fsf@suse.cz> (raw)

Hello,

we try to build coverage info for GCC for our testsuite and upload it to
https://gcc.opensuse.org/gcc-lcov/ every weekend.  But since patch
r14-1625-geba3565ce6d766 (Add support for stc and cmc instructions in
i386.md) the generation broke down.  However, I don't think there is
something necessarily wrong with that particular commit, at least I
don't see anything suspicious.

I inherited the generating script from Martin Liška and have not really
looked much into it much, but it simply does the following after a fresh
GCC master checkout (I added the --disable-multilib and reduced the
number of languages to reproduce this more quickly):


  ../src/configure --prefix=/home/mjambor/gcc/mine/inst --enable-languages=c,c++ --disable-bootstrap --enable-host-shared --enable-coverage=opt --disable-multilib
  make -j64 && make -j64 -k check
  find gcc/testsuite/ -name '*.gcda' -exec rm -rvf {} \;  # I don't know why the script does this
  lcov -d . --capture --output-file gcc.info


and this last step, since the commit, when processing file
./gcc/insn-attrtab.gcda fails with error:

  geninfo: ERROR: mismatched end line for _Z12get_attr_isaP8rtx_insn at /home/mjambor/gcc/mine/src/gcc/config/i386/i386.md:5776: 5776 -> 8963
          (use "geninfo --ignore-errors mismatch ..." to bypass this error)

I tried looking briefly into the perl sources of lcov and geninfo but I
am afraid I don't have the necessary knowledge of the language and the
tool or the time to properly debug this.  So I am inclined to simply add
--ignore-errors mismatch to lcov options, which avoids the issue, and be
done with it.  Nevertheless, I thought I'd mention this here in case
anyone here has any ideas what can be going wrong.

Thanks,

Martin

             reply	other threads:[~2023-06-16 12:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 12:51 Martin Jambor [this message]
2023-06-16 14:32 ` Roger Sayle
2023-06-25 20:11   ` Martin Jambor

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=ri6edmb4lkj.fsf@suse.cz \
    --to=mjambor@suse.cz \
    --cc=gcc@gcc.gnu.org \
    --cc=roger@nextmovesoftware.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).