[Bug testsuite/114182] gcc.c-torture/compile/attr-complex-method-2.c fails for H8/300

2024-03-03 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114182 --- Comment #3 from Jan Dubiec --- Wait a minute, shouldn't the conditions be opposite? I.e.: /* { dg-final { scan-tree-dump "__(?:gnu_)?divdc3" "optimized" { target { large_double } } } } */ /* { dg-final { scan-tree-dump "__(?:gnu_)?divsc3"

[Bug testsuite/114222] New: gcc.c-torture/execute/builtin-bitops-1.c fails for H8/300

2024-03-03 Thread jdx at o2 dot pl via Gcc-bugs
Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Host: x86_64-pc-linux-gnu Target: h8300-elf Excerpt from gcc.log: [...] Executing on host: /home/jdx/testgcc/builddir/gcc

[Bug testsuite/114182] gcc.c-torture/compile/attr-complex-method-2.c fails for H8/300

2024-03-03 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114182 --- Comment #2 from Jan Dubiec --- Unfortunately, large_double does not work.

[Bug testsuite/114221] New: gcc.c-torture/execute/20101011-1.c fails for H8/300

2024-03-03 Thread jdx at o2 dot pl via Gcc-bugs
Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Host: x86_64-pc-linux-gnu Target: h8300-elf Excerpt from gcc.sum: [...] PASS: gcc.c-torture/execute/20101011-1.c -O0 (test for excess errors

[Bug testsuite/114182] New: gcc.c-torture/compile/attr-complex-method-2.c fails for H8/300

2024-02-29 Thread jdx at o2 dot pl via Gcc-bugs
Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Host: x86_64-pc-linux-gnu Target: h8300-elf Created attachment 57581 --> https://gcc.gnu.org/bugzi

[Bug libstdc++/114085] New: Internal (cross) compiler error when building libstdc++ for the H8/300 family

2024-02-23 Thread jdx at o2 dot pl via Gcc-bugs
: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Host: x86_64-pc-linux-gnu Target: h8300-elf Created attachment 57519 --> https://gcc.gnu.

[Bug binutils/31333] New: Unused variable in binutils/sim/common/dv-sockser.c

2024-02-02 Thread jdx at o2 dot pl
Component: binutils Assignee: unassigned at sourceware dot org Reporter: jdx at o2 dot pl Target Milestone: --- Host: x86_64-w64-mingw32 Target: h8300-elf This is what happened when I tried to build rev. e58beedf for H8: [...] CC h8300

[Bug other/113147] Building a crosscompiler fails under MigW-W64/MSYS2 @ Windows 10

2023-12-30 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113147 --- Comment #2 from Jan Dubiec --- (In reply to Andrew Pinski from comment #1) > Don't use `--disable-host-shared` basically. OK, removal of this option seems to solve the problem, but... I had an impression that the above set of options

[Bug other/113147] New: Building a crosscompiler fails under MigW-W64/MSYS2 @ Windows 10

2023-12-26 Thread jdx at o2 dot pl via Gcc-bugs
Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Host: x86_64-w64-mingw32 Target: h8300-elf, arm-elf The following error occurs when I try

[Bug libgcc/109289] Conflicting types for built-in functions in libgcc/emutls.c

2023-12-02 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109289 --- Comment #6 from Jan Dubiec --- (In reply to Florian Weimer from comment #3) > Jan, do you actually experience a build failure? The part you quoted only > shows warnings. Florian, it used to be just the warnings, but now (commit 1461b431) I

[Bug target/111170] New: Malformed manifest does not allow to run gcc on Windows XP (Accessing a corrupted shared library)

2023-08-27 Thread jdx at o2 dot pl via Gcc-bugs
: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl CC: costas.argyris at gmail dot com Target Milestone: --- Target: i686-w64-mingw32 @ Windows XP

[Bug target/109324] Genrecog reports "source missing a mode?" for H8

2023-04-08 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109324 --- Comment #2 from Jan Dubiec --- It seems that msp430-elf has similar problem: build/genrecog.exe ../../../gcc/gcc/common.md ../../../gcc/gcc/config/msp430/msp430.md \ insn-conditions.md > tmp-recog.cc

[Bug target/109324] New: Genrecog reports "source missing a mode?" for H8

2023-03-28 Thread jdx at o2 dot pl via Gcc-bugs
ty: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Target: h8300-elf Unfortunately, I barely understand .md files, but I think genrecog is a bit overzealous. It would be nice if thes

[Bug other/109293] [12 Regression] Missing memmem() prototype in fixincludes/fixfixes.c on Windows/MinGW-W64

2023-03-28 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109293 --- Comment #9 from Jan Dubiec --- I can confirm that now everything is fine on this issue on Windows/MingW.

[Bug other/109293] New: Missing memmem() prototype in fixincludes/fixfixes.c on Windows/MinGW-W64

2023-03-27 Thread jdx at o2 dot pl via Gcc-bugs
: build Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Host: x86_64-w64-mingw32 Created attachment 54763 --> https://gcc.gnu.org/bugzi

[Bug libgcc/109289] New: Conflicting types for built-in functions in libgcc/emutls.c

2023-03-26 Thread jdx at o2 dot pl via Gcc-bugs
Priority: P3 Component: libgcc Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Created attachment 54759 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54759=edit Proposed patch For different hosts (Windows/MSYS2, Li

[Bug libgcc/109286] Assembler warnings about .init/.fini sections defined without attributes

2023-03-26 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109286 --- Comment #2 from Jan Dubiec --- $ h8300-elf-as --version GNU assembler (GNU Toolchain for Renesas H8 Family [Built by jdx]) 2.40 Copyright (C) 2023 Free Software Foundation, Inc. This program is free software; you may redistribute it under

[Bug libgcc/109286] Assembler warnings about .init/.fini sections defined without attributes

2023-03-26 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109286 --- Comment #1 from Jan Dubiec --- Created attachment 54758 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54758=edit crtend.S

[Bug libgcc/109286] New: Assembler warnings about .init/.fini sections defined without attributes

2023-03-26 Thread jdx at o2 dot pl via Gcc-bugs
: inline-asm, internal-improvement Severity: normal Priority: P3 Component: libgcc Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Host: x86_64-w64-mingw32 Target: h8300-elf Created

[Bug libgcc/109285] New: Unused variable in function __fixunssfdi

2023-03-26 Thread jdx at o2 dot pl via Gcc-bugs
Priority: P3 Component: libgcc Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Host: x86_64-w64-mingw32 Target: h8300-elf Created attachment 54756 --> https://gcc.gnu.org/bugzilla/attachment.cgi

[Bug bootstrap/109188] Building genmodes under MinGW-W64/MSYS2 fails due to undefined HOST_EXTRA_OBJS_SYMBOL

2023-03-23 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109188 --- Comment #13 from Jan Dubiec --- I have applied the patch posted yesterday on PR108865 and everything seems to be fine.

[Bug bootstrap/109188] Building genmodes under MinGW-W64/MSYS2 fails due to undefined HOST_EXTRA_OBJS_SYMBOL

2023-03-19 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109188 --- Comment #12 from Jan Dubiec --- Yes, there is such a snippet in gcc/Makefile.in but I have completely no idea what you mean.

[Bug bootstrap/109188] Building genmodes under MinGW-W64/MSYS2 fails due to undefined HOST_EXTRA_OBJS_SYMBOL

2023-03-19 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109188 --- Comment #10 from Jan Dubiec --- (In reply to Andrew Pinski from comment #9) > Can you change $(COMPILERS) to cc1 in gcc/config/i386/x-mingw32-utf8 and see > if that helps? I have changed it and I can confirm that genmodes.exe has been

[Bug bootstrap/109188] Building genmodes under MinGW-W64/MSYS2 fails due to undefined HOST_EXTRA_OBJS_SYMBOL

2023-03-19 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109188 --- Comment #8 from Jan Dubiec --- Output of another important command: $ uname -a MINGW64_NT-10.0-19045 jdxpc 3.4.6.x86_64 2023-02-15 18:03 UTC x86_64 Msys

[Bug bootstrap/109188] Building genmodes under MinGW-W64/MSYS2 fails due to undefined HOST_EXTRA_OBJS_SYMBOL

2023-03-19 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109188 --- Comment #7 from Jan Dubiec --- Make version is 4.4.1 as comment #2 shows. Usually I call make from my bash build script using "make 2>&1 | tee buildlog-gcc.txt", but I tried to build native compiler by simply calling "make" from the bash

[Bug bootstrap/109188] Building genmodes under MinGW-W64/MSYS2 fails due to undefined HOST_EXTRA_OBJS_SYMBOL

2023-03-19 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109188 --- Comment #5 from Jan Dubiec --- I forgot to mention it in the first message – at least h8300-elf and mips-elf are also affected. I have just even tried to build native compiler and, strangely, it has the same issue.

[Bug bootstrap/109188] Building genmodes under MinGW-W64/MSYS2 fails due to undefined HOST_EXTRA_OBJS_SYMBOL

2023-03-19 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109188 --- Comment #3 from Jan Dubiec --- I have just finished painful "git bisect" and found the offending commit: https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=d11e088210a551235d3937f867ee1c8b19d02290. However I do not know where the bug is.

[Bug target/109166] Built-in __atomic_test_and_set does not seem to be atomic on ARMv4T

2023-03-19 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109166 --- Comment #5 from Jan Dubiec --- I read that thread a few days ago and I understand concerns regarding SWP, in particular on ARMv6 which has made SWP obsolete (AFAIR it is optional on ARMv6-A/R, ARMv6-M has neither SWP nor LDREX/STREX).

[Bug bootstrap/109188] Building genmodes under MinGW-W64/MSYS2 fails due to undefined HOST_EXTRA_OBJS_SYMBOL

2023-03-19 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109188 --- Comment #2 from Jan Dubiec --- jdx@jdxpc MINGW64 /d/works/xcomp $ make --version GNU Make 4.4.1 Built for x86_64-pc-msys Copyright (C) 1988-2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

[Bug other/109189] Format string warnings in gcc/config/h8300/h8300.cc under MigW-W64/MSYS2

2023-03-19 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109189 --- Comment #1 from Jan Dubiec --- BTW, it would be nice if someone experienced could inspect lines 1547–1553, 1572–1578 and 1751–1757 in that file. These ranges contain code which looks like this: case CONST_DOUBLE: {

[Bug other/109189] New: Format string warnings in gcc/config/h8300/h8300.cc under MigW-W64/MSYS2

2023-03-19 Thread jdx at o2 dot pl via Gcc-bugs
: internal-improvement Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Host: x86_64-w64-mingw32 Target: h8300-elf Created attachment 54704

[Bug c/109188] New: Building genmodes under MinGW-W64/MSYS2 fails due to undefined HOST_EXTRA_OBJS_SYMBOL

2023-03-19 Thread jdx at o2 dot pl via Gcc-bugs
Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Host: x86_64-w64-mingw32 Target: arm-eabi I get the following error message when I try to build

[Bug target/109166] Built-in __atomic_test_and_set does not seem to be atomic on ARMv4T

2023-03-19 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109166 --- Comment #3 from Jan Dubiec --- I do not get what "but that requires more" means in this context. Lets assume that two threads test and set the same memory location which initial value is 0 ("unlocked"/"false"). Now, when the first thread

[Bug target/109166] New: Built-in __atomic_test_and_set does not seem to be atomic on ARMv4T

2023-03-16 Thread jdx at o2 dot pl via Gcc-bugs
Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Host: x86_64-w64-mingw32 Target: arm-eabi For the following source code: bool tas(unsigned char *ptr

[Bug gold/30171] Building gold fails under MinGW-W64/MSYS2 on Windows 10

2023-03-06 Thread jdx at o2 dot pl
https://sourceware.org/bugzilla/show_bug.cgi?id=30171 --- Comment #4 from Jan Dubiec --- Created attachment 14734 --> https://sourceware.org/bugzilla/attachment.cgi?id=14734=edit Preferred patch This is my preferred patch. It uses load-time dynamic linking instead of run-time dynamic linking,

[Bug gold/30171] Building gold fails under MinGW-W64/MSYS2 on Windows 10

2023-03-06 Thread jdx at o2 dot pl
https://sourceware.org/bugzilla/show_bug.cgi?id=30171 --- Comment #3 from Jan Dubiec --- Created attachment 14733 --> https://sourceware.org/bugzilla/attachment.cgi?id=14733=edit Proposed patch (Yoda style) -- You are receiving this mail because: You are on the CC list for the bug.

[Bug gold/30171] Building gold fails under MinGW-W64/MSYS2 on Windows 10

2023-03-06 Thread jdx at o2 dot pl
https://sourceware.org/bugzilla/show_bug.cgi?id=30171 --- Comment #2 from Jan Dubiec --- Created attachment 14732 --> https://sourceware.org/bugzilla/attachment.cgi?id=14732=edit Proposed patch -- You are receiving this mail because: You are on the CC list for the bug.

[Bug gold/30170] Building gold fails on MinGW-W64/MSYS2 on indows 10

2023-02-25 Thread jdx at o2 dot pl
https://sourceware.org/bugzilla/show_bug.cgi?id=30170 Jan Dubiec changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug gold/30171] Building gold fails under MinGW-W64/MSYS2 on Windows 10

2023-02-25 Thread jdx at o2 dot pl
https://sourceware.org/bugzilla/show_bug.cgi?id=30171 --- Comment #1 from Jan Dubiec --- *** Bug 30170 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

[Bug gold/30171] New: Building gold fails under MinGW-W64/MSYS2 on Windows 10

2023-02-25 Thread jdx at o2 dot pl
Priority: P2 Component: gold Assignee: ccoutant at gmail dot com Reporter: jdx at o2 dot pl CC: ian at airs dot com Target Milestone: --- Host: x86_64-w64-mingw32 I got the following error when I tried to build master (95ebc6fd

[Bug gold/30170] New: Building gold fails on MinGW-W64/MSYS2 on indows 10

2023-02-25 Thread jdx at o2 dot pl
Component: gold Assignee: ccoutant at gmail dot com Reporter: jdx at o2 dot pl CC: ian at airs dot com Target Milestone: --- Host: x86_64-w64-mingw32 make[4]: Entering directory '/d/Works/xcomp/binutils-build/gold' CXX archive.o

[Bug other/108662] Cast between incompatible function types in libiberty/physmem.c under MinGW-W64/MSYS2 on Windows 10

2023-02-05 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108662 --- Comment #1 from Jan Dubiec --- Created attachment 54410 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54410=edit Proposed patch

[Bug other/108662] New: Cast between incompatible function types in libiberty/physmem.c under MinGW-W64/MSYS2 on Windows 10

2023-02-03 Thread jdx at o2 dot pl via Gcc-bugs
Status: UNCONFIRMED Keywords: internal-improvement Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Host: x86_64-w64-mingw32

[Bug other/108644] Format string warnings related to longs under MigW-W64/MSYS2 on Windows 10

2023-02-03 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108644 --- Comment #7 from Jan Dubiec --- (In reply to Andrew Pinski from comment #6) [...] > as sizeof returns size_t. > > Does that make sense now? Yep, thanks.

[Bug other/108644] Format string warnings related to longs under MigW-W64/MSYS2 on Windows 10

2023-02-03 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108644 --- Comment #5 from Jan Dubiec --- Andrew, as per your wish, preprocessed lto-plugin\lto-plugin.c is in the attachment. It was produced using the following command: gcc -DHAVE_CONFIG_H -I. -I../../../gcc/lto-plugin

[Bug other/108644] Format string warnings related to longs under MigW-W64/MSYS2 on Windows 10

2023-02-03 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108644 --- Comment #4 from Jan Dubiec --- Created attachment 54406 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54406=edit Preprocessed lto-plugin\lto-plugin.c

[Bug other/108644] New: Format string warnings related to longs under MigW-W64/MSYS2 on Windows 10

2023-02-02 Thread jdx at o2 dot pl via Gcc-bugs
: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Host: x86_64-w64-mingw32 Build: x86_64-w64-mingw32 Below are three excerpts from my gcc's build log. I

[Bug libstdc++/108221] Building cross compiler for H8 family fails at libstdc++-v3/src/c++20/tzdb.cc

2023-01-30 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108221 --- Comment #21 from Jan Dubiec --- Unfortunately, after recent changes compilation for H8 family ends with: Making all in c++20 make[5]: Entering directory '/d/Works/xcomp/gcc-build/h8300-elf/libstdc++-v3/src/c++20' echo 'static const char

[Bug libstdc++/108221] Building cross compiler for H8 family fails at libstdc++-v3/src/c++20/tzdb.cc

2023-01-13 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108221 --- Comment #19 from Jan Dubiec --- (In reply to Jonathan Wakely from comment #17) > (but I still get the assembler errors for h8300-elf using > latest binutils). This is strange. I have just successfully built binutils edf64cd2 and then gcc

[Bug libstdc++/108221] Building cross compiler for H8 family fails at libstdc++-v3/src/c++20/tzdb.cc

2023-01-11 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108221 --- Comment #18 from Jan Dubiec --- Thanks Jonathan. I confirm – I have successfully built master (554bb9b6) for both targets. Although I'm still using binutils 2.39, I haven't tried its current master yet.

[Bug libstdc++/108221] Building cross compiler for H8 family fails at libstdc++-v3/src/c++20/tzdb.cc

2023-01-08 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108221 --- Comment #13 from Jan Dubiec --- FYI, Jonathan. This time the target is msp430-elf. Making all in c++20 make[9]: Entering directory '/d/Works/xcomp/gcc-build/msp430-elf/large/libstdc++-v3/src/c++20' /bin/sh ../../libtool --tag CXX --tag

[Bug libstdc++/108221] Building cross compiler for H8 family fails at libstdc++-v3/src/c++20/tzdb.cc

2023-01-07 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108221 --- Comment #11 from Jan Dubiec --- (In reply to Jonathan Wakely from comment #8) > (In reply to Jan Dubiec from comment #6) > > Please note -mn -mint32 options – > > normal mode (aka 16-bit mode) with 32-bit integers. > > Has this bizarre

[Bug libstdc++/108221] Building cross compiler for H8 family fails at libstdc++-v3/src/c++20/tzdb.cc

2023-01-06 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108221 --- Comment #6 from Jan Dubiec --- Jonathan, I am not sure to what part of the thread "above" refers to, but build fails indeed. This time due to a different reason. This is what I got when I was trying to build f7bd48c6. Please note -mn

[Bug libstdc++/108221] New: Building cross compiler for H8 family fails at libstdc++-v3/src/c++20/tzdb.cc

2022-12-25 Thread jdx at o2 dot pl via Gcc-bugs
: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Host: x86_64-w64-mingw32 Target: h8300-elf Build: x86_64-w64-mingw32 I get following

[Bug libstdc++/107801] Building cross compiler for H8 family fails in libstdc++ (c++17/memory_resource.cc)

2022-12-04 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107801 --- Comment #17 from Jan Dubiec --- Thanks Jonathan. I have also applied g:7b79fa930917da735f02b4f6911dfbb0a91f9714 and finally successfully built libstdc++, however there is a bunch of warnings for review. There are no assembler errors for

[Bug libstdc++/107801] Building cross compiler for H8 family fails in libstdc++ (c++17/memory_resource.cc)

2022-11-29 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107801 --- Comment #15 from Jan Dubiec --- I have applied the patch manually to 12.2 tree and this time got following error message: /bin/sh ../../libtool --tag CXX --tag disable-shared --mode=compile /d/Works/xcomp/gcc-build/./gcc/xgcc

[Bug libstdc++/107801] Building cross compiler for H8 family fails in libstdc++ (c++17/memory_resource.cc)

2022-11-26 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107801 --- Comment #9 from Jan Dubiec --- I think I have found why the static assertion fails as mentioned in my previous comment. Surprisingly, for H8/300H, H8/S and H8/SX in normal mode 32-bit integers and floats are aligned on 4-byte boundaries.

[Bug target/107878] Incomplete documentation for H8/300

2022-11-26 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107878 --- Comment #2 from Jan Dubiec --- One more thing – the documentation on the webpage states that -mn "must be used either with -mh or -ms". It is true for old compilers (e.g. for gcc 4.7 which I still use) but does not seem to be true for new

[Bug other/107878] New: Incomplete documentation for H8/300

2022-11-26 Thread jdx at o2 dot pl via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- Documentation on https://gcc.gnu.org/onlinedocs/gcc-12.2.0/gcc/H8_002f300-Options.html is not consistent with /gcc/config/h8300/h8300.opt. E.g. -msx option is not mentioned on the webpage.

[Bug libstdc++/107801] Building cross compiler for H8 family fails in libstdc++ (c++17/memory_resource.cc)

2022-11-22 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107801 --- Comment #7 from Jan Dubiec --- OK, I have applied the patch manually to my 12.2.0 tree and libstdc++ has been partially build. "Partially" because everything seems to be fine for H8/300H, H8S and H8SX in "advanced mode" (let's call it

[Bug libstdc++/107801] Building cross compiler for H8 family fails in libstdc++ (c++17/memory_resource.cc)

2022-11-22 Thread jdx at o2 dot pl via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107801 --- Comment #5 from jdx at o2 dot pl --- (In reply to CVS Commits from comment #4) > The releases/gcc-12 branch has been updated by Jonathan Wakely > : > > https://gcc.gnu.org/g:691012693aaa831e4cd1ab5180195792e32baceb > &g

[Bug libstdc++/107801] New: Building cross compiler for H8 family fails in libstdc++ (c++17/memory_resource.cc)

2022-11-21 Thread jdx at o2 dot pl via Gcc-bugs
Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: jdx at o2 dot pl Target Milestone: --- I am trying to build under MingW64/Windows 10 the toolchain for H8 using following steps: 1. build binutils and install