From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17897 invoked by alias); 21 Sep 2015 11:04:26 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 17857 invoked by uid 48); 21 Sep 2015 11:04:23 -0000 From: "manu at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/60832] add pretty-printer code for double-int/wide-int Date: Mon, 21 Sep 2015 11:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: diagnostic, easyhack X-Bugzilla-Severity: normal X-Bugzilla-Who: manu at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-09/txt/msg01687.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D60832 --- Comment #3 from Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez --- Created attachment 36361 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D36361&action=3Dedit add %Wi %Wu %Wd for pretty-printing wides_int This fails bootstrap at: libcommon.a(pretty-print.o): In function `pp_format(pretty_printer*, text_info*)': /home/manuel/test1/src/gcc/pretty-print.c:543: undefined reference to `print_dec(generic_wide_int > const&, char*, signop)' /home/manuel/test1/src/gcc/pretty-print.c:573: undefined reference to `print_dec(generic_wide_int > const&, char*, signop)' collect2: error: ld returned 1 exit status make: *** [gcov] Error 1 pretty-print.c is used all over the place and adding a dependency on wide-int.cc will bring gmp and other stuff that is currently not used (nor linked with) various helper programs. If wide-int is only printed in the middle-end, perhaps it is sufficient to add it to default_tree_printer. Otherwise, it needs to be added to every FE. This is not difficult just tedious. The difficult part is the c-format.c changes (I wish someone would= fix https://gcc.gnu.org/PR47781 so we can use a simpler syntax to define our cu= stom specifiers; in addition to the positive synergies it will bring with other = GNU projects that use custom specifiers and wish to use -Wformat). >>From gcc-bugs-return-497710-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Sep 21 11:17:25 2015 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 72999 invoked by alias); 21 Sep 2015 11:17:24 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 72959 invoked by uid 48); 21 Sep 2015 11:17:21 -0000 From: "miyuki at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/67649] trunk build with valgrind fail in get_def_blocks_for Date: Mon, 21 Sep 2015 11:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: miyuki at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-09/txt/msg01688.txt.bz2 Content-length: 315 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67649 --- Comment #7 from Mikhail Maltsev --- Probably. Will look at this today (valgrind has some sort of memory pool API, I think it can be used here). I need to configure GCC with --enable-checking=yes,valgrind to reproduce this, right?