Gcc: reload pass and "reload_completed" in backend.md files

Question

Gcc: reload pass and "reload_completed" in backend.md files

I am working on a new backend for GCC and am getting help from existing machine description files for various purposes.

So far I don't understand the following:

What does skipping reboot do?
How does he interact with the combine? I see a lot of "reload_completed" errors in the MDC files of the MIPS file. Why are some define_insn_and_split templates with "reload_completed" and others without?

I've tried reading about what overloading goes through here and also tried some archive searches on gcc-help. However, what the reload is, what it achieves, and its interaction with other passes, such as the harvester pass, is not clear to me. Can anyone elaborate on this in more detail with examples?

+3

gcc compiler-construction compilation

Cherry vanc 25 Aug 14 at 23:31

source to share

No one has answered this question yet

Check out similar questions:

1938

Why doesn't GCC optimize a * a * a * a * a * a to (a * a * a) * (a * a * a)?

996

Fatal error: Python.h: No such file or directory

783

What is the difference between g ++ and gcc?

296

GCC Option -fPIC

86

Is the definition “volatile” this volatile, or does GCC have some standard conformance problems?

nine

Gcc functions with constructor attribute are not bound

4

What the -f and -m options in gcc / clang mean to the compiler

3

Linking include files in GCC

2

Register GIMPLE pass in gcc 5.1.0

1

Placing Spatter Skips During GCC Compilation

Gcc: reload pass and "reload_completed" in backend.md files

More articles: