public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/108854] [10/11/12/13 Regression] tbb-2021.8.0 fails on i686-linux (32-bit), internal compiler error: in expand_expr_real_1, at expr.c:10281
Date: Wed, 22 Feb 2023 15:40:59 +0000	[thread overview]
Message-ID: <bug-108854-4-7MtIElSGRd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108854-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|needs-reduction             |
           Priority|P3                          |P2
   Target Milestone|---                         |10.5
                 CC|                            |hubicka at gcc dot gnu.org,
                   |                            |jamborm at gcc dot gnu.org
            Summary|tbb-2021.8.0 fails on       |[10/11/12/13 Regression]
                   |i686-linux (32-bit),        |tbb-2021.8.0 fails on
                   |internal compiler error: in |i686-linux (32-bit),
                   |expand_expr_real_1, at      |internal compiler error: in
                   |expr.c:10281                |expand_expr_real_1, at
                   |                            |expr.c:10281

--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Reduced testcase for -m32 -O3 -std=c++11 -fPIC:

struct unique_scoped_lock {
  unique_scoped_lock(int);
  ~unique_scoped_lock();
};
struct rw_scoped_lock {
  rw_scoped_lock(int, bool);
  ~rw_scoped_lock();
};
template <typename _Tp> struct Trans_NS___cxx11_list {
  typedef _Tp value_type;
  void push_front(value_type);
  void push_back(value_type &&);
};
class receiver typedef node_priority_t;
struct graph_node {
  virtual void reset_node();
};
template <typename> struct sender {
  typedef receiver successor_type;
  virtual bool register_successor(successor_type &);
};
struct receiver {
  virtual node_priority_t priority() { return receiver(); }
};
void fgt_make_edge(void *, void *);
struct successor_cache {
  int my_mutex;
  Trans_NS___cxx11_list<receiver *> my_successors;
  void register_successor(receiver &r) {
    rw_scoped_lock l(my_mutex, true);
    r.priority();
    my_successors.push_front(&r);
    my_successors.push_back(&r);
  }
};
struct input_node : graph_node, sender<int> {
  template <typename Body> input_node(int, Body);
  bool register_successor(successor_type &r) {
    unique_scoped_lock lock(my_mutex);
    my_successors.register_successor(r);
    if (my_active)
      return true;
  }
  int my_mutex;
  bool my_active;
  successor_cache my_successors;
};
inline void make_edge(sender<int> &p) {
  receiver s, __trans_tmp_2;
  p.register_successor(__trans_tmp_2);
  fgt_make_edge(&p, &s);
}
enum TestNodeTypeEnum { nonThrowing, isThrowing };
template <TestNodeTypeEnum> struct absorber_body;
template <class, class InputNodeType, class, class, class, class>
void run_one_priority_queue_node_test() {
  int g, input_count;
  InputNodeType input(g, input_count);
  make_edge(input);
}
template <class, int, TestNodeTypeEnum SinkThrowType>
void run_priority_queue_node_test() {
  run_one_priority_queue_node_test<int, input_node, int, int, graph_node,
                                   absorber_body<SinkThrowType>>();
}
void test_priority_queue_node() {
  run_priority_queue_node_test<int, isThrowing, nonThrowing>();
  run_priority_queue_node_test<int, isThrowing, isThrowing>();
}

This started to ICE (segfault in same_node_or_its_all_contexts_clone_p) with
r10-4511-g6cf67b62c8cda035dccac and starting with
r10-5061-g68188fff88d0c302e6002 it gets the
ICE that shows up to latest trunk.

  parent reply	other threads:[~2023-02-22 15:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-19 23:53 [Bug c++/108854] New: tbb-2021.8.0 fails on i686-linux (32-bit) gcc.gnu.org+lufm at davidak dot de
2023-02-20  8:34 ` [Bug middle-end/108854] tbb-2021.8.0 fails on i686-linux (32-bit), internal compiler error: in expand_expr_real_1, at expr.c:10281 rguenth at gcc dot gnu.org
2023-02-20  9:52 ` jakub at gcc dot gnu.org
2023-02-20 12:14 ` redi at gcc dot gnu.org
2023-02-20 23:31 ` pinskia at gcc dot gnu.org
2023-02-20 23:39 ` pinskia at gcc dot gnu.org
2023-02-21 17:00 ` gcc.gnu.org+lufm at davidak dot de
2023-02-21 18:32 ` jakub at gcc dot gnu.org
2023-02-22  9:40 ` slyfox at gcc dot gnu.org
2023-02-22 13:22 ` jakub at gcc dot gnu.org
2023-02-22 15:40 ` jakub at gcc dot gnu.org [this message]
2023-02-23 15:55 ` [Bug middle-end/108854] [10/11/12/13 Regression] tbb-2021.8.0 fails on i686-linux (32-bit), internal compiler error: in expand_expr_real_1, at expr.c:10281 since r10-4511-g6cf67b62c8cda035dccac jakub at gcc dot gnu.org
2023-02-23 16:16 ` jakub at gcc dot gnu.org
2023-02-24 10:06 ` cvs-commit at gcc dot gnu.org
2023-02-24 10:07 ` [Bug middle-end/108854] [10/11/12 " jakub at gcc dot gnu.org
2023-03-19  5:29 ` cvs-commit at gcc dot gnu.org
2023-03-20 10:27 ` [Bug middle-end/108854] [10/11 " jakub at gcc dot gnu.org
2023-05-02 20:15 ` cvs-commit at gcc dot gnu.org
2023-05-03 10:39 ` [Bug middle-end/108854] [10 " jakub at gcc dot gnu.org
2023-05-03 15:21 ` cvs-commit at gcc dot gnu.org
2023-05-04  7:25 ` 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-108854-4-7MtIElSGRd@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).