public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 6/7] diagnostics: eliminate diagnostic_context::m_print_path callback
Date: Tue, 18 Jun 2024 14:22:01 -0400	[thread overview]
Message-ID: <3f5a3236e1315b544e70366b2fc8ebd89bdc7f8f.camel@redhat.com> (raw)
In-Reply-To: <20240618150819.946820-7-dmalcolm@redhat.com>

On Tue, 2024-06-18 at 11:08 -0400, David Malcolm wrote:
> No functional change intended.

Sorry, it looks like I should have combined patches 6 and 7, in that
patch 6 temporarily breaks the build:

e.g.:
  https://builder.sourceware.org/buildbot/#/builders/156/builds/10063

make[2]: Leaving directory '/home/mjw/wildebeest/buildbot/gcc-fedora-ppc64le/gcc-build/gcc'
g++ -no-pie   -g -O2     -DIN_GCC    -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Wconditionally-supported -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings   -DHAVE_CONFIG_H -no-pie  gcov-dump.o \
	hash-table.o ggc-none.o\
	libcommon.a ../libcpp/libcpp.a   ../libbacktrace/.libs/libbacktrace.a ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a  -o gcov-dump
/usr/bin/ld: libcommon.a(diagnostic.o): in function `diagnostic_context::show_any_path(diagnostic_info const&)':
/home/mjw/wildebeest/buildbot/gcc-fedora-ppc64le/gcc-build/gcc/../../gcc/gcc/diagnostic.cc:918:(.text+0x2084): undefined reference to `diagnostic_context::print_path(diagnostic_path const*)'
/usr/bin/ld: /home/mjw/wildebeest/buildbot/gcc-fedora-ppc64le/gcc-build/gcc/../../gcc/gcc/diagnostic.cc:918:(.text+0x4a34): undefined reference to `diagnostic_context::print_path(diagnostic_path const*)'
collect2: error: ld returned 1 exit status

Should be fixed by patch 7 in the kit, which puts that symbol in
libcommon.a; am continuing to watch the post-commit CI.

Sorry again
Dave


  reply	other threads:[~2024-06-18 18:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18 15:08 [pushed 0/7] diagnostics: remove "tree" dependency from diagnostic paths David Malcolm
2024-06-18 15:08 ` [PATCH 1/7] diagnostics: move simple_diagnostic_{path,thread,event} to their own .h/cc David Malcolm
2024-06-18 15:08 ` [PATCH 2/7] diagnostics: eliminate "tree" from diagnostic_{event,path} David Malcolm
2024-06-18 15:08 ` [PATCH 3/7] diagnostics: remove tree usage from tree-diagnostic-path.cc David Malcolm
2024-06-18 15:08 ` [PATCH 4/7] diagnostics: eliminate diagnostic_context::m_make_json_for_path David Malcolm
2024-06-18 15:08 ` [PATCH 5/7] diagnostics: introduce diagnostic-macro-unwinding.h/cc David Malcolm
2024-06-18 15:08 ` [PATCH 6/7] diagnostics: eliminate diagnostic_context::m_print_path callback David Malcolm
2024-06-18 18:22   ` David Malcolm [this message]
2024-06-18 15:08 ` [PATCH 7/7] diagnostics: rename tree-diagnostic-path.cc to diagnostic-path.cc David Malcolm

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=3f5a3236e1315b544e70366b2fc8ebd89bdc7f8f.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).