public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eyalroz1 at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/113188] New: graphite-isl-ast-to-gimple.c: ‘isl_val_free’ was not declared in this scope
Date: Mon, 01 Jan 2024 09:27:54 +0000	[thread overview]
Message-ID: <bug-113188-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113188
           Summary: graphite-isl-ast-to-gimple.c: ‘isl_val_free’ was not
                    declared in this scope
           Product: gcc
           Version: 6.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: eyalroz1 at gmx dot com
  Target Milestone: ---

I'm struggling trying to build GCC 6.5.0 on a newer system: Devuan GNU/Linux
Excalibur (~= Debian Trixie). I'm using the following configuration:

./configure --disable-libsanitizer --disable-bootstrap --enable-languages=c,c++

and at some point, I get a couple of compilation errors about undeclared
identifiers; the error is quoted below.

Is there some way I could circumvent these? e.g. by disabling another component
or replacing a version of some tool/library?

-----------------



g++ -fno-PIE -c   -g -O2 -DIN_GCC     -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic
-Wno-long-long -Wno-variadic-macros -Wno-overlength-strings   -DHAVE_CONFIG_H
-I. -I. -I../.././gcc -I../.././gcc/. -I../.././gcc/../include
-I../.././gcc/../libcpp/include  -I../.././gcc/../libdecnumber
-I../.././gcc/../libdecnumber/bid -I../libdecnumber
-I../.././gcc/../libbacktrace   -o graphite-isl-ast-to-gimple.o -MT
graphite-isl-ast-to-gimple.o -MMD -MP -MF
./.deps/graphite-isl-ast-to-gimple.TPo ../.././gcc/graphite-isl-ast-to-gimple.c
../.././gcc/graphite-isl-ast-to-gimple.c: In member function ‘tree_node*
translate_isl_ast_to_gimple::gcc_expression_from_isl_expr_int(tree,
isl_ast_expr*)’:
../.././gcc/graphite-isl-ast-to-gimple.c:349:3: error: ‘isl_val_free’ was not
declared in this scope; did you mean ‘isl_vec_free’?
  349 |   isl_val_free (val);
      |   ^~~~~~~~~~~~
      |   isl_vec_free
../.././gcc/graphite-isl-ast-to-gimple.c: In function ‘isl_ast_expr*
get_upper_bound(isl_ast_node*)’:
../.././gcc/graphite-isl-ast-to-gimple.c:752:11: error: ‘isl_val_int_from_si’
was not declared in this scope; did you mean ‘isl_val_int_from_gmp’?
  752 |           isl_val_int_from_si (isl_ast_expr_get_ctx (for_cond), 1);
      |           ^~~~~~~~~~~~~~~~~~~
      |           isl_val_int_from_gmp

             reply	other threads:[~2024-01-01  9:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-01  9:27 eyalroz1 at gmx dot com [this message]
2024-01-01  9:36 ` [Bug other/113188] " pinskia at gcc dot gnu.org
2024-01-06  5:53 ` pinskia 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-113188-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).