public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108698] New: [13 Regression] decltype ((T() + ‘excess_precision_expr’ not supported by dump_expr<expression error>)) median(ndarray<T>) [with T = double]’: since  r13-3290-g98e341130f87984a
Date: Tue, 07 Feb 2023 14:09:44 +0000	[thread overview]
Message-ID: <bug-108698-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 108698
           Summary: [13 Regression] decltype ((T() +
                    ‘excess_precision_expr’ not supported by
                    dump_expr<expression error>)) median(ndarray<T>) [with
                    T = double]’: since  r13-3290-g98e341130f87984a
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Keywords: rejects-valid
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
  Target Milestone: ---
              Host: x86_64-linux-gnu

The following is isolated from python-scipy package:

$ cat scipy.ii
template <class> struct ndarray {};
template <class T> decltype(T() + 1.) median(ndarray<T>);
struct Trans_NS_functor_median {
  template <typename... Types> void operator()(Types...) { median(Types()...);
}
};
struct siegelslopes {
  void operator()(siegelslopes, double, void()) {
    ndarray<double> __trans_tmp_9;
    Trans_NS_functor_median{}(__trans_tmp_9);
  }
} siegelslopes0_y;
double siegelslopes0_x;
void siegelslopes0_method() {
  siegelslopes()(siegelslopes0_y, siegelslopes0_x, siegelslopes0_method);
}

$ g++ scipy.ii -c -m32 -std=c++14
scipy.ii: In instantiation of ‘decltype ((T() + ‘excess_precision_expr’ not
supported by dump_expr<expression error>)) median(ndarray<T>) [with T =
double]’:
scipy.ii:2:39: sorry, unimplemented: mangling excess_precision_expr
    2 | template <class T> decltype(T() + 1.) median(ndarray<T>);
      |                                       ^~~~~~

$ g++-12 scipy.ii -c -m32 -std=c++14

             reply	other threads:[~2023-02-07 14:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 14:09 marxin at gcc dot gnu.org [this message]
2023-02-07 14:09 ` [Bug tree-optimization/108698] " marxin at gcc dot gnu.org
2023-02-07 16:33 ` [Bug c++/108698] " jakub at gcc dot gnu.org
2023-02-07 19:38 ` jakub at gcc dot gnu.org
2023-02-07 19:38 ` jakub at gcc dot gnu.org
2023-02-09  8:32 ` cvs-commit at gcc dot gnu.org
2023-02-09  8:34 ` jakub 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-108698-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).