How do I report some extremely weird (useless) code generated by GDC when the -O3 option is used? (bizarre rats’ nest of conditional jumps). [I am an experienced professional asm programmer, now retired.]

The D source is short, fortunately. The asm output I am looking at is seen through the telescope that is Matt GodBolt’s Compiler Explorer at http://explore.dgnu.org so I possibly would want to pull the asm text from that site (somehow).

On Tuesday, 20 March 2018 at 23:06:23 UTC, Cecil Ward wrote:
> How do I report some extremely weird (useless) code generated by GDC when the -O3 option is used? (bizarre rats’ nest of conditional jumps). [I am an experienced professional asm programmer, now retired.]
>
> The D source is short, fortunately. The asm output I am looking at is seen through the telescope that is Matt GodBolt’s Compiler Explorer at http://explore.dgnu.org so I possibly would want to pull the asm text from that site (somehow).

Bugs can be filed at https://bugzilla.gdcproject.org/

Mike

Am Tue, 20 Mar 2018 23:06:23 +0000 schrieb Cecil Ward:

> How do I report some extremely weird (useless) code generated by GDC when the -O3 option is used? (bizarre rats’ nest of conditional jumps). [I am an experienced professional asm programmer, now retired.]
> 
> The D source is short, fortunately. The asm output I am looking at is seen through the telescope that is Matt GodBolt’s Compiler Explorer at http://explore.dgnu.org so I possibly would want to pull the asm text from that site (somehow).


Just post the link in your bug report on bugzilla.gdcproject.org. Preferably also attach the source code and asm as files, for archiving purposes. Or if the source and asm is short enough simply post it inline.

-- 
Johannes