public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113045] New: armv7l-unknown-linux-gnueabihf: valgrind error during build of libcc1
Date: Sat, 16 Dec 2023 16:39:57 +0000 [thread overview]
Message-ID: <bug-113045-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113045
Bug ID: 113045
Summary: armv7l-unknown-linux-gnueabihf: valgrind error during
build of libcc1
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
I just tried a valgrind build of gcc trunk on my Raspberry PI 3B+.
It said:
echo | /home/dcb/gcc/working/./gcc/xgcc -B/home/dcb/gcc/working/./gcc/
-nostdinc -E -dM - | \
sed -n -e 's/^#define \([^_][a-zA-Z0-9_]*\).*/\1/p' \
-e 's/^#define \(_[^_A-Z][a-zA-Z0-9_]*\).*/\1/p' | \
sort -u > tmp-macro_list
==9933== Invalid read of size 8
==9933== at 0x151D554: vld1q_u8 (arm_neon.h:10455)
==9933== by 0x151D554: search_line_fast (lex.cc:872)
==9933== by 0x151D554: _cpp_clean_line (lex.cc:960)
==9933== by 0x151DA0F: bool get_fresh_line_impl<false>(cpp_reader*)
(lex.cc:3747)
$ grep -E "^Config|^==[0-9]" mk.out
Configuring in ./libiberty
Configuring in ./fixincludes
Configuring in ./lto-plugin
Configuring in build-armv7l-unknown-linux-gnueabihf/libiberty
Configuring in build-armv7l-unknown-linux-gnueabihf/fixincludes
Configuring in build-armv7l-unknown-linux-gnueabihf/libcpp
Configuring in ./zlib
Configuring in ./libbacktrace
Configuring in ./libcody
Configuring in ./libdecnumber
Configuring in ./c++tools
Configuring in ./libcpp
Configuring in ./gcc
Configuring in ./libcc1
==9933== Invalid read of size 8
==9933== at 0x151D554: vld1q_u8 (arm_neon.h:10455)
==9933== by 0x151D554: search_line_fast (lex.cc:872)
==9933== by 0x151D554: _cpp_clean_line (lex.cc:960)
==9933== by 0x151DA0F: bool get_fresh_line_impl<false>(cpp_reader*)
(lex.cc:3
747)
Configure line is
../trunk/configure --disable-multilib \
--disable-bootstrap \
--enable-checking=valgrind \
--enable-languages=c,c++
And there is some tweeking of the top level Makefile:
sed 's;-O2;-O2 -march=native;' < Makefile > Makefile.tmp
diff Makefile Makefile.tmp
mv Makefile.tmp Makefile
next reply other threads:[~2023-12-16 16:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 16:39 dcb314 at hotmail dot com [this message]
2023-12-16 16:44 ` [Bug target/113045] " pinskia at gcc dot gnu.org
2023-12-17 17:35 ` dcb314 at hotmail dot com
2023-12-17 18:18 ` redi at gcc dot gnu.org
2023-12-17 18:21 ` redi at gcc dot gnu.org
2023-12-17 18:50 ` dcb314 at hotmail dot com
2023-12-17 18:57 ` dcb314 at hotmail dot com
2023-12-17 19:55 ` dcb314 at hotmail dot com
2023-12-17 20:06 ` pinskia at gcc dot gnu.org
2023-12-17 20:11 ` pinskia at gcc dot gnu.org
2023-12-17 21:05 ` redi at gcc dot gnu.org
2023-12-17 22:22 ` redi at gcc dot gnu.org
2023-12-17 22:25 ` redi at gcc dot gnu.org
2023-12-18 8:18 ` rguenth at gcc dot gnu.org
2023-12-19 8:23 ` dcb314 at hotmail dot com
2023-12-19 8:28 ` dcb314 at hotmail dot com
2023-12-19 9:22 ` redi at gcc dot gnu.org
2023-12-19 12:58 ` mark at gcc dot gnu.org
2023-12-19 16:53 ` dcb314 at hotmail dot com
2023-12-19 17:18 ` mark at gcc dot gnu.org
2024-01-02 14:40 ` rearnsha at gcc dot gnu.org
2024-01-02 14:49 ` rearnsha at gcc dot gnu.org
2024-01-02 15:05 ` dcb314 at hotmail dot com
2024-01-02 15:14 ` schwab@linux-m68k.org
2024-01-02 15:18 ` rearnsha at gcc dot gnu.org
2024-01-02 16:25 ` mark at gcc dot gnu.org
2024-01-02 16:28 ` rearnsha at gcc dot gnu.org
2024-01-02 16:35 ` rearnsha at gcc dot gnu.org
2024-01-02 17:23 ` rearnsha at gcc dot gnu.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-113045-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).