public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/109984] New: FAIL: insn-modes.h: No such file or directory (x86_64-apple-darwin22.4.0)
@ 2023-05-26  9:39 gcc-zm31 at proton dot me
  2023-05-26 17:25 ` [Bug target/109984] " pinskia at gcc dot gnu.org
  0 siblings, 1 reply; 2+ messages in thread
From: gcc-zm31 at proton dot me @ 2023-05-26  9:39 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 109984
           Summary: FAIL: insn-modes.h: No such file or directory
                    (x86_64-apple-darwin22.4.0)
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gcc-zm31 at proton dot me
  Target Milestone: ---

When attempting to build GCC with an experimental language frontend, I
encounter the following error:

In file included from ../../gcc-src/gcc/rinto/rin-system.hpp:30,
                 from ../../gcc-src/gcc/rinto/frontend/backend.hpp:4,
                 from ../../gcc-src/gcc/rinto/frontend/diagnostic.hpp:37,
                 from ../../gcc-src/gcc/rinto/frontend/diagnostic.cc:33:
../../gcc-src/gcc/coretypes.h:458:10: fatal error: insn-modes.h: No such file
or directory
  458 | #include "insn-modes.h"

This only seems to be an issue when passing the -j flag to make. When I
otherwise run 'make' on a single processor (without -j), the project compiles.
I suspect there might be some oversight on my part, though it could be an issue
with the order in which GCC generates header files.

The project is configured as follows:
../gcc-src/configure --prefix=/Users/mz/Desktop/gcc-build/../gcc-install
--enable-languages=c,c++,rinto
--with-sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk
--disable-nls --enable-checking=release --with-gcc-major-version-only
--with-system-zlib

And the make command:
make -j$(getconf _NPROCESSORS_ONLN)

where 'getconf _NPROCESSORS_ONLN; yields 16.

Target: x86_64-apple-darwin22.4.0 (though the problem persists on my Ubuntu 22
machine as well). 

SOURCE-A: https://github.com/rintolang/rinto/tree/main/src/gcc
SOURCE-B: https://github.com/rintolang/rinto/tree/main/src/frontend

The contents of SOURCE-A are placed in [GCC-ROOT]/gcc/rinto and SOURCE-B in
[GCC-ROOT]/gcc/rinto/frontend.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug target/109984] FAIL: insn-modes.h: No such file or directory (x86_64-apple-darwin22.4.0)
  2023-05-26  9:39 [Bug target/109984] New: FAIL: insn-modes.h: No such file or directory (x86_64-apple-darwin22.4.0) gcc-zm31 at proton dot me
@ 2023-05-26 17:25 ` pinskia at gcc dot gnu.org
  0 siblings, 0 replies; 2+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-05-26 17:25 UTC (permalink / raw)
  To: gcc-bugs

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This is not the right place to ask about a bug in your front-end.

If you use coretypes.h you need to specify $(CORETYPES_H) as a depedency on
those object files.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-05-26 17:25 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-05-26  9:39 [Bug target/109984] New: FAIL: insn-modes.h: No such file or directory (x86_64-apple-darwin22.4.0) gcc-zm31 at proton dot me
2023-05-26 17:25 ` [Bug target/109984] " pinskia at gcc dot gnu.org

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).