On Friday, 22 March 2024 at 15:12:16 UTC, redthing1 wrote:
On Tuesday, 18 May 2021 at 14:43:52 UTC, Imperatorn wrote:
On Tuesday, 18 May 2021 at 08:40:10 UTC, Iain Buclaw wrote:
On Monday, 17 May 2021 at 11:08:33 UTC, Raimondo Mancino
wrote:
[...]
The command would be pretty much the same
On Sunday, 14 April 2024 at 16:04:54 UTC, Matheus Catarino wrote:
Espressif/LLVM have xtensa-ABI (windowed) partial support, but
GCC [upstream and fork] have both xtensa-ABI (call0 & windowed)
OK.
BTW. If you are on Debian / Ubuntu, xtensa cross compilers for
C,C++,D are prepackaged in
On Sunday, 14 April 2024 at 07:25:07 UTC, Witold Baryluk wrote:
On Friday, 12 April 2024 at 23:16:30 UTC, Matheus Catarino
wrote:
I've recently seen support for different target architectures
on https://explore.dgnu.org .
What is the status of Xtensa and xtensa-gnu support? Does it
support
On Friday, 12 April 2024 at 23:16:30 UTC, Matheus Catarino wrote:
I've recently seen support for different target architectures
on https://explore.dgnu.org .
What is the status of Xtensa and xtensa-gnu support? Does it
support both xtensa ABIs (call0 and windowed)?
Currently there is a need
I've recently seen support for different target architectures on
https://explore.dgnu.org .
What is the status of Xtensa and xtensa-gnu support? Does it
support both xtensa ABIs (call0 and windowed)?
Currently there is a need to fork espressif/LLVM when using ldc2.
Is there a need to fork
On Saturday, 23 March 2024 at 17:41:15 UTC, Iain Buclaw wrote:
On Wednesday, 20 March 2024 at 13:19:27 UTC, Mahdis wrote:
[...]
To point out a few things you may not already be aware of /
offer some thoughts in what I hope reads as neutral.
[...]
https://www.jinftry.com/
On Wednesday, 20 March 2024 at 13:19:27 UTC, Mahdis wrote:
Hi,
I have a question about the possibility of developing a new
frontend language for GIMPLE in GCC using D instead of C++.
To point out a few things you may not already be aware of / offer
some thoughts in what I hope reads as
On Tuesday, 18 May 2021 at 14:43:52 UTC, Imperatorn wrote:
On Tuesday, 18 May 2021 at 08:40:10 UTC, Iain Buclaw wrote:
On Monday, 17 May 2021 at 11:08:33 UTC, Raimondo Mancino wrote:
[...]
The command would be pretty much the same as gcc (`-nostdinc
-nostdlib`), but instead of `-include
Hi,
I have a question about the possibility of developing a new
frontend language for GIMPLE in GCC using D instead of C++.
I'm interested in exploring this possibility because D offers
several advantages over C++, including:
1. Memory safety: D's garbage collector eliminates the need for
On Tuesday, 22 August 2023 at 15:25:25 UTC, jicman wrote:
On Wednesday, 7 June 2023 at 18:04:43 UTC, Ferhat Kurtulmuş
wrote:
[...]
Ok, maybe we can get this fixed, somehow. :-)
[...]
Any progress on getting cygwin GDC to work?
Tim S.
On 15/01/2024 1:23 AM, pizza_dox_ wrote:
On Sunday, 14 January 2024 at 11:54:09 UTC, Richard (Rikki) Andrew
Cattermole wrote:
On 15/01/2024 12:47 AM, pizza_dox_ wrote:
OK to make it clear. I wanted to call d from c so that I can write a
n64 game with d. But compiling the d object
On Sunday, 14 January 2024 at 11:54:09 UTC, Richard (Rikki)
Andrew Cattermole wrote:
On 15/01/2024 12:47 AM, pizza_dox_ wrote:
OK to make it clear. I wanted to call d from c so that I can
write a n64 game with d. But compiling the d object files
while using higher features like classes,
On 15/01/2024 12:47 AM, pizza_dox_ wrote:
OK to make it clear. I wanted to call d from c so that I can write a n64
game with d. But compiling the d object files while using higher
features like classes, resulted in missing dependencys. So because GCC
doesnt understands d I need an object
OK to make it clear. I wanted to call d from c so that I can
write a n64 game with d. But compiling the d object files while
using higher features like classes, resulted in missing
dependencys. So because GCC doesnt understands d I need an object
file which has everything included d needs to
On 15/01/2024 12:42 AM, pizza_dox_ wrote:
On Sunday, 14 January 2024 at 10:05:12 UTC, Richard (Rikki) Andrew
Cattermole wrote:
On 08/01/2024 7:14 AM, Renato wrote:
On Friday, 5 January 2024 at 22:10:31 UTC, pizza_dox_ wrote:
[...]
Did you try using dub and specifying
On Sunday, 14 January 2024 at 10:05:12 UTC, Richard (Rikki)
Andrew Cattermole wrote:
On 08/01/2024 7:14 AM, Renato wrote:
On Friday, 5 January 2024 at 22:10:31 UTC, pizza_dox_
wrote:
[...]
Did you try using dub and specifying
`targetType="staticLibrary"`?
See
On 08/01/2024 7:14 AM, Renato wrote:
On Friday, 5 January 2024 at 22:10:31 UTC, pizza_dox_ wrote:
Hi, I am trying with gdc to create the equivalent of a fat jar. So for
that I would need the standard dlang library included in the object or
library file. Does somebody know the needed gdc
On Sunday, 14 January 2024 at 09:36:16 UTC, pizza_dox_ wrote:
On Sunday, 7 January 2024 at 18:14:12 UTC, Renato wrote:
On Friday, 5 January 2024 at 22:10:31 UTC, pizza_dox_
wrote:
Hi, I am trying with gdc to create the equivalent of a fat
jar. So for that I would need the standard
On Sunday, 7 January 2024 at 18:14:12 UTC, Renato wrote:
On Friday, 5 January 2024 at 22:10:31 UTC, pizza_dox_ wrote:
Hi, I am trying with gdc to create the equivalent of a fat
jar. So for that I would need the standard dlang library
included in the object or library file. Does somebody
On Tuesday, 2 January 2024 at 03:14:05 UTC, Siarhei Siamashka
wrote:
On Tuesday, 2 January 2024 at 01:49:47 UTC, Siarhei Siamashka
wrote:
Thanks for giving the Windows users this hint. It's much
better than the radio silence.
And by the way, I'm not being sarcastic. Having any hints is
On Friday, 5 January 2024 at 22:10:31 UTC, pizza_dox_ wrote:
Hi, I am trying with gdc to create the equivalent of a fat jar.
So for that I would need the standard dlang library included in
the object or library file. Does somebody know the needed gdc
flags?
I am using
Hi, I am trying with gdc to create the equivalent of a fat jar.
So for that I would need the standard dlang library included in
the object or library file. Does somebody know the needed gdc
flags?
I am using mips64-linux-gnuabi64-gdc-12.
pizza_dox_
On Tuesday, 2 January 2024 at 01:49:47 UTC, Siarhei Siamashka
wrote:
Thanks for giving the Windows users this hint. It's much better
than the radio silence.
And by the way, I'm not being sarcastic. Having any hints is
really useful for the potential contributors.
On Tuesday, 2 January 2024 at 00:07:39 UTC, Iain Buclaw wrote:
Might not be best to wait for me to port it, as anything on
Windows tends to get sidetracked given that I have no access to
any machine running it.
I have an obsolete 32-bit Windows 7 preinstalled on a single-core
Atom 1.66GHz
On Monday, 1 January 2024 at 23:59:38 UTC, Siarhei Siamashka
wrote:
On Monday, 1 January 2024 at 23:49:41 UTC, tdm3j2bqz wrote:
Is gdc known to work on Cygwin?
There's already a discussion thread about this:
https://forum.dlang.org/thread/ndoljmmelsslcjvrs...@forum.dlang.org
Might not be
On Monday, 1 January 2024 at 23:49:41 UTC, tdm3j2bqz wrote:
Is gdc known to work on Cygwin?
There's already a discussion thread about this:
https://forum.dlang.org/thread/ndoljmmelsslcjvrs...@forum.dlang.org
This is from a regular Cygwin package called gcc-gdc installed
after the gcc-core package was installed.
```
$ gdc hello.d -o hello
d21: error: cannot find source code for runtime library file
'object.d'
d21: note: dmd might not be correctly installed. Run 'dmd -man'
for installation
On Friday, 11 August 2023 at 05:50:43 UTC, Joe Kappus wrote:
I noticed this yesterday when trying to package the dlang
onedrive client in Gentoo with GDC 13.2 and it failed since it
requires this.
It appears to have been removed when gdc became self-hosting in
gcc during the gcc-12 release
Did you solve it?
No, project delayed until I'll have enough deep qualification in
system-level D coding
On Wednesday, 25 October 2023 at 17:11:11 UTC, Dmitry Ponyatov
wrote:
How/where are you referencing mmap64? Could some include be
missing or path issue?
ref/gcc-12.3.0/libphobos/libdruntime/core/internal/gc/os.d:145
ref/gcc-12.3.0/libphobos/libdruntime/core/thread/fiber.d:1050
How/where are you referencing mmap64? Could some include be
missing or path issue?
ref/gcc-12.3.0/libphobos/libdruntime/core/internal/gc/os.d:145
ref/gcc-12.3.0/libphobos/libdruntime/core/thread/fiber.d:1050
host/lib/gcc/i686-linux-musl/12.3.0/../../../../i686-linux-musl/lib/libgphobos.a(os.o)
On Sunday, 22 October 2023 at 21:52:18 UTC, Dmitry Ponyatov wrote:
[...]
fixed by moving to `musl` usage -- not a surprise that `uClibc`
becomes obsoleted libc comparing their compilation time,
configuration complexity, and incompatibility with modern
toolchains
[...]
How/where are you
Here the next problem of building `gcc-12.3.0` with
`uClibc-ng-1.0.44` (i386 target):
fixed by moving to `musl` usage -- not a surprise that `uClibc`
becomes obsoleted libc comparing their compilation time,
configuration complexity, and incompatibility with modern
toolchains
But the next
I'm following a tutorial that offers this file (start.s),
.section ".text.boot"
.globl _start
_start:
la sp, _stack_start
call dstart
_hlt:
j _hlt # jump to _hlt
...assembled with this,
**riscv64-unknown-elf-as -mno-relax -march=rv64imac start.s -c
-o
Here the next problem of building `gcc-12.3.0` with
`uClibc-ng-1.0.44` (i386 target):
```
libtool: compile:
/home/ponyatov/player/tmp/gcc-12.3.0-1/./gcc/gdc
-B/home/ponyatov/player/tmp/gcc-12.3.0-1/./gcc/
-B/home/ponyatov/player/host/i686-linux-uclibc/bin/
You'll need at least gcc-9/gdc-9 to build gcc-13.
Version problem was fixed by building `gcc-12.3.0` with `gdc`
enabled on local host, and using it for the whole build in place
of system-provided `gcc` toolchain.
```Makefile
# version
GCC_VER = 12.3.0
```
```Makefile
# tool
GDCH =
On Saturday, 21 October 2023 at 23:13:57 UTC, Dmitry Ponyatov
wrote:
```sh
gdc --version
```
```
gdc (Debian 8.3.0-6) 8.3.0
```
You'll need at least gcc-9/gdc-9 to build gcc-13.
```sh
gdc --version
```
```
gdc (Debian 8.3.0-6) 8.3.0
```
I'm trying to build a tiny Linux system with cross-compiling GDB:
https://github.com/ponyatov/player/blob/shadow/Makefile
```
BINUTILS_VER = 2.41
GCC_VER = 13.2.0
```
```sh
cat /etc/os-release
```
```
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
On Saturday, 14 October 2023 at 19:28:59 UTC, Johann wrote:
On Saturday, 14 October 2023 at 19:01:53 UTC, Iain Buclaw wrote:
On Saturday, 14 October 2023 at 17:53:01 UTC, Johann wrote:
I cannot figure out this error is caused by `squiz_box`
libray, `gdc` or `dub`. My apologies to you if I
On Saturday, 14 October 2023 at 19:01:53 UTC, Iain Buclaw wrote:
On Saturday, 14 October 2023 at 17:53:01 UTC, Johann wrote:
I cannot figure out this error is caused by `squiz_box`
libray, `gdc` or `dub`. My apologies to you if I should have
filed this bug in other places. Thanks for your
On Saturday, 14 October 2023 at 17:53:01 UTC, Johann wrote:
I cannot figure out this error is caused by `squiz_box` libray,
`gdc` or `dub`. My apologies to you if I should have filed this
bug in other places. Thanks for your attention.
Based on the symbol names, it could be this PR, which was
On Saturday, 14 October 2023 at 18:15:11 UTC, Richard (Rikki)
Andrew Cattermole wrote:
The frontend will attempt to not emit all template
instantiations if it thinks that the instantiation isn't used.
However it sometimes get this wrong, so you have to override it
and tell it to emit them all
The frontend will attempt to not emit all template instantiations if it
thinks that the instantiation isn't used. However it sometimes get this
wrong, so you have to override it and tell it to emit them all anyway
and let the linker do the eliding instead.
This is a known problem of all the
On Saturday, 14 October 2023 at 17:58:27 UTC, Richard (Rikki)
Andrew Cattermole wrote:
This may be a simple case of template emission eliding.
Did you try ``-fall-instantiations`` inside of a dflags
directive?
Yeah, that works perfectly, thank you a lot.
This may be a simple case of
This may be a simple case of template emission eliding.
Did you try ``-fall-instantiations`` inside of a dflags directive?
The following is a project created by `dub init`.
dub.json
```json
{
"authors": [
"john"
],
"dependencies": {
"squiz-box": {
"repository":
"git+https://github.com/rtbo/squiz-box.git;,
On Friday, 11 August 2023 at 05:50:43 UTC, Joe Kappus wrote:
I noticed this yesterday when trying to package the dlang
onedrive client in Gentoo with GDC 13.2 and it failed since it
requires this.
It appears to have been removed when gdc became self-hosting in
gcc during the gcc-12 release
On Thursday, 31 August 2023 at 13:53:55 UTC, Zachary Yedidia
wrote:
The following code generates a warning when using GCC analyzer,
but I don't think the warning is valid.
```
struct Guard {
~this() {}
}
Guard lock() {
return Guard();
}
void bar() {
auto foo = lock();
}
```
On Thursday, 31 August 2023 at 13:53:55 UTC, Zachary Yedidia
wrote:
The following code generates a warning when using GCC analyzer,
but I don't think the warning is valid.
```
struct Guard {
~this() {}
}
Guard lock() {
return Guard();
}
void bar() {
auto foo = lock();
}
```
The following code generates a warning when using GCC analyzer,
but I don't think the warning is valid.
```
struct Guard {
~this() {}
}
Guard lock() {
return Guard();
}
void bar() {
auto foo = lock();
}
```
Compiled with GCC version 13.1:
```
$ gdc -fanalyzer test.d -O2 -c
test.d:
On Tuesday, 22 August 2023 at 15:25:25 UTC, jicman wrote:
On Wednesday, 7 June 2023 at 18:04:43 UTC, Ferhat Kurtulmuş
wrote:
[...]
Ok, maybe we can get this fixed, somehow. :-)
[...]
Not sure but there should be a config file similar to LDC's
ldc2.conf but for GDC.
On Wednesday, 7 June 2023 at 18:04:43 UTC, Ferhat Kurtulmuş wrote:
I ve been waiting for an answer for this question too. GDC has
lack of windows support for ages.
Ok, maybe we can get this fixed, somehow. :-)
I installed GDC from cygwin's setup tool. If I run,
```
$ gdc -v
Using built-in
On Wednesday, 9 August 2023 at 12:51:51 UTC, Adam D Ruppe wrote:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110959
Related DMD bug - the backporting of which looks like it'd fix
your test case too. https://issues.dlang.org/show_bug.cgi?id=23010
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110959
On Wednesday, 9 August 2023 at 12:44:16 UTC, Iain Buclaw wrote:
Can you raise a bug report against gcc.gnu.org/bugzilla?
yeah i just got the email approving the account a minute ago.
didn't take as long as i thought it would lol
On Wednesday, 9 August 2023 at 11:48:41 UTC, Adam D Ruppe wrote:
$ cat gdcbug.d
class ArsdExceptionBase : object.Exception {
package this(string operation, string file = __FILE__,
size_t line = __LINE__, Throwable next = null) {
super(operation, file, line, next);
$ gdc --version
gdc (GCC) 12.2.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
$ gdc gdcbug.d
gdcbug.d: In function ‘D main’:
On Wednesday, 26 July 2023 at 04:35:43 UTC, Chris Piker wrote:
Is that a feature that is likely, or unlikely, to be added to a
future version of GDC?
I expect it to be incremental. There's a POC implementation that
uses the built-in preprocessor that already exists in gdc
(libcpp),
Hi GDC
Over at: https://gcc.gnu.org/onlinedocs/gdc/Missing-Features.html
I read that GDC doesn't invoke the preprocessor automatically:
```
ImportC Limitations
GNU D does not run the preprocessor automatically for any
ImportC sources. Instead all C files are expected to be manually
On Tuesday, 11 July 2023 at 18:08:30 UTC, mw wrote:
Hi,
Currently,
```
$ gdc-12 --version
gdc-12 (Ubuntu 12.1.0-2ubuntu1~22.04) 12.1.0
$ gdc-12 -dumpversion
12
```
this is not very informative, as D (DMD) language is always
changing, Can gdc --version or -dumpversion output the
Hi,
Currently,
```
$ gdc-12 --version
gdc-12 (Ubuntu 12.1.0-2ubuntu1~22.04) 12.1.0
$ gdc-12 -dumpversion
12
```
this is not very informative, as D (DMD) language is always
changing, Can gdc --version or -dumpversion output the
corresponding DMD front-end (language) version?
just as LDC
On Saturday, 1 July 2023 at 16:53:10 UTC, Johann wrote:
On Saturday, 1 July 2023 at 15:36:55 UTC, Johann wrote:
On Saturday, 1 July 2023 at 10:18:43 UTC, Iain Buclaw wrote:
Is it too much to ask downstream package maintainers to
politely use `/usr/share/dlang/{ldc,dmd}` ? :-)
Thanks for your
On Saturday, 1 July 2023 at 15:36:55 UTC, Johann wrote:
On Saturday, 1 July 2023 at 10:18:43 UTC, Iain Buclaw wrote:
Is it too much to ask downstream package maintainers to
politely use `/usr/share/dlang/{ldc,dmd}` ? :-)
Thanks for your help, Iain. I am going to report a bug to the
distro
On Saturday, 1 July 2023 at 10:18:43 UTC, Iain Buclaw wrote:
Is it too much to ask downstream package maintainers to
politely use `/usr/share/dlang/{ldc,dmd}` ? :-)
Thanks for your help, Iain. I am going to report a bug to the
distro maintainers then.
On Saturday, 1 July 2023 at 06:53:02 UTC, Johann wrote:
I have both `ldc` and `gdc` install on my OpenSUSE tumbleweed
machine.
` Without `ldc-runtime-devel`, `gdc` is able to compile
successfully.
[--snip--]
How may I fix it? I tried to use "-I" and "-B" option, but to
no avail.
Looks
On Thursday, 8 June 2023 at 11:39:38 UTC, Iain Buclaw wrote:
On Thursday, 8 June 2023 at 04:13:30 UTC, Cecil Ward wrote:
I wrote a very small procedure in D and the x86-64 asm code
generated in GDC 12.3 was excellent whereas that from 13.1 was
insanely bloated, totally different. Note: the
I have both `ldc` and `gdc` install on my OpenSUSE tumbleweed
machine.
Without `ldc-runtime-devel`, `gdc` is able to compile
successfully.
```bash
binary/usr/lib64/gcc/x86_64-suse-linux/13/d21
version v2.103.0-rc.1
predefs GNU D_Version2 LittleEndian GNU_DWARF2_Exceptions
On Thursday, 29 June 2023 at 09:18:19 UTC, Iain Buclaw wrote:
On Thursday, 29 June 2023 at 05:27:57 UTC, Cecil Ward wrote:
I tried getting GCC on my ARM M2 Mac using the homebrew
package manager, which is how I got LDC. It gave me C++ and C
and FORTRAN, but no sign of any GDC.
How is GCC
On Thursday, 29 June 2023 at 05:27:57 UTC, Cecil Ward wrote:
I tried getting GCC on my ARM M2 Mac using the homebrew package
manager, which is how I got LDC. It gave me C++ and C and
FORTRAN, but no sign of any GDC.
How is GCC available when it has no support for aarch64-darwin2x?
I tried getting GCC on my ARM M2 Mac using the homebrew package
manager, which is how I got LDC. It gave me C++ and C and
FORTRAN, but no sign of any GDC.
On Monday, 19 June 2023 at 09:54:32 UTC, Iain Buclaw wrote:
On Sunday, 18 June 2023 at 02:55:32 UTC, Cecil Ward wrote:
On Friday, 16 June 2023 at 13:12:06 UTC, Iain Buclaw wrote:
Redundant jump? Yes, arguably. Leads to wrong runtime?
Doesn't look that way.
Completely agree with Iain, it’s
On Sunday, 18 June 2023 at 02:55:32 UTC, Cecil Ward wrote:
On Friday, 16 June 2023 at 13:12:06 UTC, Iain Buclaw wrote:
Redundant jump? Yes, arguably. Leads to wrong runtime? Doesn't
look that way.
Completely agree with Iain, it’s not incorrect code, I wasn’t
intending to suggest that. I’d
On Friday, 16 June 2023 at 13:12:06 UTC, Iain Buclaw wrote:
On Wednesday, 14 June 2023 at 12:35:43 UTC, Cecil Ward wrote:
I have just noticed a bug in the latest release of GDC that
targets x86-64. For example GDC 12.3 and above versions too,
running on X86-64, targeting self. This was built
On Wednesday, 14 June 2023 at 12:35:43 UTC, Cecil Ward wrote:
I have just noticed a bug in the latest release of GDC that
targets x86-64. For example GDC 12.3 and above versions too,
running on X86-64, targeting self. This was built with:
-O3 -frelease -march=alderlake
What leads you to
I have just noticed a bug in the latest release of GDC that
targets x86-64. For example GDC 12.3 and above versions too,
running on X86-64, targeting self. This was built with:
-O3 -frelease -march=alderlake
Generated code is:
je L1
jbe L1
…
…
L1: ret
The probably reason for
On Thursday, 8 June 2023 at 04:13:30 UTC, Cecil Ward wrote:
I wrote a very small procedure in D and the x86-64 asm code
generated in GDC 12.3 was excellent whereas that from 13.1 was
insanely bloated, totally different. Note: the badness is
independent of the -On optimisation level (-O3 used
I wrote a very small procedure in D and the x86-64 asm code
generated in GDC 12.3 was excellent whereas that from 13.1 was
insanely bloated, totally different. Note: the badness is
independent of the -On optimisation level (-O3 used initially.)
Here’s the D code and following it, two asm code
On Wednesday, 7 June 2023 at 17:47:06 UTC, jicman wrote:
On Tuesday, 6 June 2023 at 18:55:31 UTC, jicman wrote:
Greetings!
I was very happy to see GDC available on cygwin, but, the list
said, "...and without a working runtime the next major release
of gcc will again have to drop it as it
On Tuesday, 6 June 2023 at 18:55:31 UTC, jicman wrote:
Greetings!
I was very happy to see GDC available on cygwin, but, the list
said, "...and without a working runtime the next major release
of gcc will again have to drop it as it would no longer
bootstrap." Has a decision being made of not
Greetings!
I was very happy to see GDC available on cygwin, but, the list
said, "...and without a working runtime the next major release of
gcc will again have to drop it as it would no longer bootstrap."
Has a decision being made of not supporting cygwin? Thanks.
josé
On Sunday, 7 May 2023 at 13:41:43 UTC, WebFreak001 wrote:
I have multiple GDCs installed through apt, how do I make gdmd
pick the higher one (`gdc-12`) and not just `gdc`?
With e.g. `ln -s gdmd /usr/bin/gdmd-12`, and then using
`gdmd-12`. As shown by the few linked lines in the Perl script,
On Thursday, 4 May 2023 at 14:58:48 UTC, Iain Buclaw wrote:
On Thursday, 4 May 2023 at 13:05:07 UTC, WebFreak001 wrote:
In GitHub Actions I installed `sudo apt install gdc-12` now
inside Ubuntu 22.04, however `gdc` still seemed to be a small
extra package that's symlinking gdc to gdc-11.
Now
On Thursday, 4 May 2023 at 13:05:07 UTC, WebFreak001 wrote:
In GitHub Actions I installed `sudo apt install gdc-12` now
inside Ubuntu 22.04, however `gdc` still seemed to be a small
extra package that's symlinking gdc to gdc-11.
Now gdmd is picking up GDC 11 instead of GDC 12, causing issues
In GitHub Actions I installed `sudo apt install gdc-12` now
inside Ubuntu 22.04, however `gdc` still seemed to be a small
extra package that's symlinking gdc to gdc-11.
Now gdmd is picking up GDC 11 instead of GDC 12, causing issues
in the build.
Is there a way to tell gdmd to use GDC 12?
D is cancer
Hi,
On Wednesday, 14 December 2022 at 22:23:49 UTC, Witold Baryluk
wrote:>
The bulk of information is in `.debug_info`. But I believe it
contains way more information than is really needed to just
produce line numbers.
You're observation is correct. GDC uses libbacktrace to produce
On Tuesday, 20 December 2022 at 02:19:33 UTC, Iain Buclaw wrote:
On Monday, 19 December 2022 at 14:00:38 UTC, Brian Callahan
wrote:
Hi Iain --
GDC mainline stopped building on OpenBSD recently. Below is
the diff to fix things.
[...]
Thanks, better to send that to upstr dmd though (I did
On Monday, 19 December 2022 at 14:00:38 UTC, Brian Callahan wrote:
Hi Iain --
GDC mainline stopped building on OpenBSD recently. Below is the
diff to fix things.
[...]
Thanks, better to send that to upstr dmd though (I did say they
should've used @weak)
Hi Iain --
GDC mainline stopped building on OpenBSD recently. Below is the
diff to fix things.
Thanks.
~Brian
diff --git a/libphobos/libdruntime/core/demangle.d
b/libphobos/libdruntime/core/demangle.d
index 869ade64821..30e38c76479 100644
--- a/libphobos/libdruntime/core/demangle.d
+++
For example to give you some context.
This is an example small app, the actual app is significantly
larger (binary with debug symbols is about 20MB, without debug
symbols only 2-3MB).
```
$ ~/bloaty/build/bloaty binary-O3-g-g3-gz # (original binary)
FILE SIZEVM SIZE
Hi,
I am trying to split debug symbols out of final binary, to reduce
its size. But I would like to preserve at least line numbers in
the stacktraces from `Exception`s.
Linux, amd64. gdc 12.2.0 on Debian testing.
Binary is compiled using `-O3 -g -g3` (and possibly -gz).
I then use
On Sunday, 25 September 2022 at 06:03:32 UTC, Iain Buclaw wrote:
On Saturday, 24 September 2022 at 23:05:28 UTC, teverett wrote:
[...]
Hi,
I assume that this is for the [ldc
group](https://forum.dlang.org/group/ldc) instead of gdc.
Generically, building druntime should be fine, you'll
On Saturday, 24 September 2022 at 23:05:28 UTC, teverett wrote:
Hello, I am following the instructions here:
https://wiki.dlang.org/Building_LDC_runtime_libraries
I'm on OSX and need a ELF D RTL for i386.
I've used HomeBrew to install x86_64-elf-gcc, ninja and cmake.
The command I'm issuing
Hello, I am following the instructions here:
https://wiki.dlang.org/Building_LDC_runtime_libraries
I'm on OSX and need a ELF D RTL for i386.
I've used HomeBrew to install x86_64-elf-gcc, ninja and cmake.
The command I'm issuing is:
There are more issues with the GDC 11.3.0 that I compiled on
Windows earlier (it was compiled with win32 threads). The
following code has issues compiling (find_file.d):
```
import std.file;
import std.stdio;
/// Command line tool to find files in directories
int main(string[] args) {
if
https://issues.dlang.org/show_bug.cgi?id=9704
RazvanN changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
I am assuming you would like to have GDC available in the MSYS2
[MINGW32 , MINGW64, and UCRT64
environments](https://www.msys2.org/docs/environments/) (which is
what I wanted). They have an open issue in the [MINGW packages
repository](https://github.com/msys2/MINGW-packages/issues/6806)
for
On Saturday, 21 May 2022 at 21:18:15 UTC, Chris Piker wrote:
Hi GDC
I've been able to build gdc-12.1 on ubuntu20 using
```
wget
http://mirrors.concertpass.com/gcc/releases/gcc-12.1.0/gcc-12.1.0.tar.xz
tar -xvf gcc-12.1.0.tar.xz
cd gcc-12.1.0
mkdir build
cd build
../configure
The second issue was that the compilation of GCC did not work
for version gcc-11.2.0 on my version of MinGW. Many of the
configure flags resulted in warnings in the configure process
since they were not recognized (should these flags be in the
configure command?):
```
configure: WARNING:
1 - 100 of 1931 matches
Mail list logo
