public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/29104] GDB very slow running LLVM opt Date: Fri, 29 Apr 2022 22:38:44 +0000 [thread overview] Message-ID: <bug-29104-4717-FxTRohZsgK@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29104-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29104 --- Comment #7 from Martin Sebor <msebor at gmail dot com> --- GDB trunk indeed solves the problem! Thank you! $ time ~/bin/gdb-trunk/bin/gdb --batch -nx -q -ex "r -S -instcombine x.ll" /build/llvm-gcc/bin/opt This GDB supports auto-downloading debuginfo from the following URLs: <https://debuginfod.fedoraproject.org/> Enable debuginfod for this session? (y or [n]) [answered N; input not from terminal] Debuginfod has been disabled. To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". ; ModuleID = 'x.ll' source_filename = "x.ll" declare i64 @strlen(i8*) define i64 @f(i8* %s) { %n = call i64 @strlen(i8* noundef nonnull dereferenceable(1) %s) ret i64 %n } [Inferior 1 (process 133664) exited normally] real 0m1.440s user 0m10.096s -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-04-29 22:38 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-29 16:55 [Bug gdb/29104] New: " msebor at gmail dot com 2022-04-29 18:01 ` [Bug gdb/29104] " tromey at sourceware dot org 2022-04-29 18:16 ` msebor at gmail dot com 2022-04-29 19:07 ` tromey at sourceware dot org 2022-04-29 19:21 ` msebor at gmail dot com 2022-04-29 19:27 ` msebor at gmail dot com 2022-04-29 20:08 ` tromey at sourceware dot org 2022-04-29 22:38 ` msebor at gmail dot com [this message] 2022-05-09 17:31 ` tromey at sourceware dot org
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=bug-29104-4717-FxTRohZsgK@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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: linkBe 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).