public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113045] armv7l-unknown-linux-gnueabihf: valgrind error during build of libcc1 Date: Tue, 02 Jan 2024 14:49:27 +0000 [thread overview] Message-ID: <bug-113045-4-928mgQ5F3d@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113045-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113045 --- Comment #21 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- FTR it was this patch that added this code. So 2012! commit e75b54a2d932929a9b2e940c5aad1ef33a86c008 Author: Richard Earnshaw <rearnsha@arm.com> Date: Thu Mar 22 17:54:55 2012 +0000 * lex.c (search_line_fast): Provide Neon-optimized version for ARM. From-SVN: r185702 diff --git a/libcpp/ChangeLog b/libcpp/ChangeLog index 97177e89916..133620b3b70 100644 --- a/libcpp/ChangeLog +++ b/libcpp/ChangeLog @@ -1,3 +1,7 @@ +2012-03-22 Richard Earnshaw <rearnsha@arm.com> + + * lex.c (search_line_fast): Provide Neon-optimized version for ARM. +
next prev parent reply other threads:[~2024-01-02 14:49 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-16 16:39 [Bug target/113045] New: " dcb314 at hotmail dot com 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 [this message] 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-928mgQ5F3d@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: 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).