In my college days i was designing a bootloader for avr microcontroller , i had the idea to flash code wirelessly to avr over bluetooth and also cross compile the compiler for android device so that you can code on android, every thing went well just one thing didn't, i saw that code of certain size is executing properly , greater than that size gives me wired outputs so i have to dump hex from the avr (that is flashed the by bootloader) and compaire it with the original hex of code it got messy as you can see, most fun part of this bug is that error can be anywhere cross compiler may be fucked up , the bootloader may be fucked up , or it may be my bluetooth module , after 14 hours of staring at the hex code i figured out the mess in bootloader instruction that was changing the page address for flashing .

when it worked it was 3am in night i literally burst into tears of joy next day bought myself a cake to celebrate

Yesterday I was able to write a C++ compiler, a cross-platform browser, a copy of Discord and my own OS!

Then I woke up and, as always, turned on my computer and realized it was all a dream.

Im forced to work with c++ on windows for a course.

0) c++ is fucking unusable without a central repo for managing dependencies. Maybe im just too used to maven but you shouldnt be downloading dll files in 2018.

1) visual studio can go suck a fat one. I got a fairly fast pc and it takes fucking forever to load anything. For comparison, eclipse with all my plugins (and i have a lot) loads in ~10 seconds, vs2017 does in 35.

2) why the fuck is there no cross platform compilation for c++? Its supposed to run on everything right? Whats so hard about porting a fucking linux compiler so i dont realixe i have .exe files when i want to work with my laptop on the bus?

3) c++17 (? Or whatevers the newest) syntax is like a deep barf on a hot summer day after eating a whole watermelon. Its fucking unreadable and autopointers simply dont work. And its not even my lack of skill this time, its the code that the other members used and it worked for half of them.

Something they don't tell you about c++ development until it's too late: cross-compiler compatibility is an enormous monster.

When I worked with C# creating a DLL and distributing it to others is a completely transparent process, there's no special considerations required at all.

In c++ you basically aren't allowed to use the standard library in many cases. You can't just export a class with a standard string as a member because when another person goes to use your DLL, the string might have a different implementation.

A compiler and assembler set for bootstrapping the whole gcc Code tree and cross compiling each level

HELP
Why does gcc fails to compile?

main.c:10:1: error: unrecognizable insn:
10 | }
| ^
(insn/f 18 4 19 (set (mem:SI (pre_dec:SI (reg:SI 1 bx)) [0 S4 A32])
(reg:HI 0 ax)) "main.c":8:1 -1
(nil))
during RTL pass: shorten
main.c:10:1: internal compiler error: in insn_default_length, at insn-attrtab.c:221
0x61f93f _fatal_insn(char const*, rtx_def const*, char const*, int, char const*)
../../gcc/rtl-error.c:108
0x61f95b _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
../../gcc/rtl-error.c:116
0x742291 insn_default_length(rtx_insn*)
/home/user/Documents/gcc/build-d16i/gcc/insn-attrtab.c:221
0x9ee716 shorten_branches(rtx_insn*)
../../gcc/final.c:1118
0x9ee78f rest_of_handle_shorten_branches
../../gcc/final.c:4753
0x9ee78f execute
../../gcc/final.c:4782