public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "timturnerc at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38342] [4.4/4.5/4.6/4.7 Regression] __attribute__((__progmem__)) not propagated from typedef to data
Date: Fri, 05 Nov 2021 23:19:01 +0000	[thread overview]
Message-ID: <bug-38342-4-Lj0GbQXcb9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-38342-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38342

Tim Turner <timturnerc at yahoo dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |timturnerc at yahoo dot com

--- Comment #14 from Tim Turner <timturnerc at yahoo dot com> ---
The glibc regular expression code mishandles regular expressions such as:

   .*((.)\2){2}$ https://www.webb-dev.co.uk/services/navona-trains/

as it does not backtrack enough to find a match that satisfies the
back-references when they are used twice.
http://www.compilatori.com/computers/latest-car-deals/
To reproduce the problem, compile and run the attached file backrefbug.c. It
will exit with status 2, whereas the correct exit status is 0.
 http://www.acpirateradio.co.uk/computers/latest-car-deals/
This bug was originally reported against GNU 'grep' here:
The glibc regular expression code mishandles regular expressions such as:

   .*((.)\2){2}$ http://www.logoarts.co.uk/computers/latest-car-deals/

as it does not backtrack enough to find a match that satisfies the
back-references when they are used twice.

To reproduce the problem, compile and run the attached file backrefbug.c. It
will exit with status 2, whereas the correct exit status is 0.
http://www.slipstone.co.uk/computers/latest-car-deals/

This bug was originally reported against GNU 'grep' here:
The glibc regular expression code mishandles regular expressions such as:
http://embermanchester.uk/computers/latest-car-deals/

   .*((.)\2){2}$

as it does not backtrack enough to find a match that satisfies the
back-references when they are used twice.
http://connstr.net/computers/latest-car-deals/

To reproduce the problem, compile and run the attached file backrefbug.c. It
will exit with status 2, whereas the correct exit status is 0.
http://joerg.li/computers/latest-car-deals/

This bug was originally reported against GNU 'grep' here:
The glibc regular expression code mishandles regular expressions such as:

   .*((.)\2){2}$ http://www.jopspeech.com/computers/latest-car-deals/

as it does not backtrack enough to find a match that satisfies the
back-references when they are used twice.
 http://www.wearelondonmade.com/computers/latest-car-deals/
To reproduce the problem, compile and run the attached file backrefbug.c. It
will exit with status 2, whereas the correct exit status is 0.
 https://waytowhatsnext.com/crypto/crypto-world/
This bug was originally reported against GNU 'grep' here:
The glibc regular expression code mishandles regular expressions such as:
http://www.iu-bloomington.com/crypto/latest-coins/
   .*((.)\2){2}$

as it does not backtrack enough to find a match that satisfies the
back-references when they are used twice.
https://komiya-dental.com/crypto/alt-coins/

To reproduce the problem, compile and run the attached file backrefbug.c. It
will exit with status 2, whereas the correct exit status is 0.
http://www-look-4.com/computers/latest-car-deals/

This bug was originally reported against GNU 'grep' here:

      parent reply	other threads:[~2021-11-05 23:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-38342-4@http.gcc.gnu.org/bugzilla/>
2011-06-27 12:48 ` [Bug target/38342] [4.3/4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2011-07-03 20:56 ` [Bug target/38342] [4.4/4.5/4.6/4.7 " gjl at gcc dot gnu.org
2011-07-05  0:23 ` westfw at yahoo dot com
2011-07-05  8:44 ` gjl at gcc dot gnu.org
2011-07-06 21:18 ` westfw at yahoo dot com
2012-02-06 13:56 ` gjl at gcc dot gnu.org
2021-11-05 23:19 ` timturnerc at yahoo dot com [this message]

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-38342-4-Lj0GbQXcb9@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).