From: Aloz1 <Aloz1@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP]ghdl: add libbacktrace for llvm backend
Date: Wed, 22 Dec 2021 01:26:41 +0100 [thread overview]
Message-ID: <20211222002641.9PI5tWZo4KByO5sGxrLcI8D9hiK-J13s8V_2AmKTQA8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34626@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
New comment by Aloz1 on void-packages repository
https://github.com/void-linux/void-packages/pull/34626#issuecomment-999186209
Comment:
> What isn't clear to me is: does the current version not work at all, or is it simply missing the generated backtraces?
Oh, the current llvm backend works fine, it just doesn't produce backtraces, which makes debugging VHDL code quite difficult.
> Unless it provides specific functionality, I'd rather avoid that extra backend :P
As far as I can tell, the only feature that ghdl-gcc offers that other backends do not is code coverage (which is done via gcov). After mulling over this for a bit, its unimportant enough that I think dealing with the ghdl-gcc mess can be done later if absolutely necessary. I'm just using ghdl for some personal VHDL projects, so don't need code coverage.
> That sounds messy but workable, I suppose. This whole thing seems kinda wild tbh ;-;
Yeah, the whole method of using gcc as an intermediary for generating binaries is a lot more of a dogs breakfast than with llvm.
next prev parent reply other threads:[~2021-12-22 0:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 14:34 [PR PATCH] " Aloz1
2021-12-20 14:45 ` Aloz1
2021-12-20 15:05 ` [PR REVIEW] " ericonr
2021-12-20 15:05 ` ericonr
2021-12-20 15:05 ` ericonr
2021-12-20 15:32 ` Aloz1
2021-12-20 15:33 ` Aloz1
2021-12-20 15:44 ` [PR PATCH] [Updated] " Aloz1
2021-12-20 15:44 ` [PR REVIEW] " Aloz1
2021-12-21 3:37 ` ericonr
2021-12-21 6:16 ` Aloz1
2021-12-21 19:04 ` ericonr
2021-12-22 0:26 ` Aloz1 [this message]
2021-12-23 4:45 ` ericonr
2021-12-23 12:47 ` [PR PATCH] [Updated] " Aloz1
2021-12-23 12:52 ` Aloz1
2021-12-23 12:57 ` Aloz1
2021-12-23 13:03 ` Aloz1
2021-12-23 14:07 ` ericonr
2021-12-23 21:07 ` Aloz1
2021-12-23 21:07 ` Aloz1
2021-12-23 21:16 ` Aloz1
2021-12-23 22:33 ` Aloz1
2021-12-23 22:58 ` [PR PATCH] [Updated] " Aloz1
2022-01-18 11:45 ` ghdl: " Aloz1
2022-06-19 2:16 ` github-actions
2022-07-04 2:15 ` [PR PATCH] [Closed]: " github-actions
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=20211222002641.9PI5tWZo4KByO5sGxrLcI8D9hiK-J13s8V_2AmKTQA8@z \
--to=aloz1@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).