Note that there are some explanatory texts on larger screens.

plurals
  1. USacm
    primarykey
    data
    text
    plurals
    1. COOK, so with the caveat that I know essentially nothing about ARM, I would say that it means that you have another step to perform in implementing support for global ctor's and dtors for ARM. The fact that you are getting the _Z41_... symbol is encouraging, because it suggests to me that the .o file is correct. But clearly something isn't happening at link time. On x86 GCC, a link time process called collect2 handles merging all of the various static constructors into the .init section before handing off to ld (or something like that). I think linker support is your next step.
      singulars
    2. COInteresting, but it doesn't quite work. With my original version `holder<std::vector<int>> y = {1, 2, 3}` works correctly, but at least with my compiler it does not work with your revised constructor signature. It complains that 'candidate constructor template not viable: requires 1 argument, but 3 were provided'
      singulars
    3. COI know I'm nitpicking, because clearly the practical answer is "just make it const already". However, it seems to me that either it is legal to instantiate std::map with a comparator with non-const operator() as long as you don't use the map in such a way as to require constness (in which case libc++ seems to have an error where it requires comparator constness in a non-const context), or it isn't legal, and libstdc++ should reject the code above, but doesn't. Or does this somehow fall within implementation defined behavior, and so both are correct?
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload