[petsc-dev] MEMALIGN

Matthew Knepley knepley at gmail.com
Mon Aug 22 21:07:52 CDT 2016

On Mon, Aug 22, 2016 at 8:58 PM, Jed Brown <jed at jedbrown.org> wrote:

> Matthew Knepley <knepley at gmail.com> writes:
> > Not hard. We just add a flag to each value that is flipped on lookup,
> > like PETSc.
> It would be nice to be able to offer suggestions for options that
> BuildSystem queries.  For that, we need the set of command line options
> and the set of options that BuildSystem checked.  We can get that by
> having RDict implement __missing__(self, key) to consult an immutable
> dict of the direct command line options and logging the query.

Let me rephrase in order to see if I understand you. Suppose the code
checks for an option that has no value. We currently interactively prompt
for a value. You would also like us to suggest that one of the original
which is close to this was misspelled. This is not hard. However,

  1) If the option has a default value, then we cannot see that it is

  2) Those options should turn up in the unused list however

> Is it feasible to check all the options by some point meaningfully
> sooner than the entire configure execution?  It really sucks to wait
> many minutes for configure to complete only to find out that you
> misspelled an option.  Getting that error message up-front would be a
> huge usability improvement.

Right now, I am not sure how you would guarantee that the option would not
be used in the ensuing run.


> > Put it in the Issues.

What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20160822/346677c3/attachment.html>

More information about the petsc-dev mailing list