This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH/RFC] Per-architecture DWARF CFI register state initializationhooks


Since I am obviously not getting it, could someone explain to me what
the modularity advantage is?

Are you asking why modularity, in general, is advantage, or why here specifically this is more modula and hence an advantage?

The dwarf2-frame is able to locally, and opaquely (to other components) implement the per-architecture mechanisms that it needs. No need to bloat that architecture vector with yet another global interface that nothing, other than dwarf2-frame requires. No need to publish anything other than what is specificly relevant to dwarf2-frame's clients - the dwarf2 initialize routine.

All I see is a function pointer, with a default value or overridden by
the architecture initialization, used to parametrize a module's
behavior.  That is the same niche as every existing member of the
gdbarch vector.

Andrew


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]