![]() ![]() a/contrib/testsuite-management/aarch64-grtev4-linux-gnu.xfail diff -git a/contrib/testsuite-management/aarch64-grtev4-linux-gnu.xfail b/contrib/testsuite-management/aarch64-grtev4-linux-gnu.xfail diff -git a/contrib/regression/ChangeLog b/contrib/regression/ChangeLog -68,7 68,7 sparc64-elf sparc64-rtems sparc64-linux sparc64-freebsd6 \ sparc64-netbsd sparc64-openbsd spu-elf \ tilegx-linux-gnu tilegxbe-linux-gnu tilepro-linux-gnu \ - v850e-elf v850-elf vax-linux-gnu \ v850e-elf v850-elf v850-rtems vax-linux-gnu \ vax-netbsdelf vax-openbsd x86_64-apple-darwin \ x86_64-pc-linux-gnuOPT-with-fpmath=avx \ x86_64-elfOPT-with-fpmath=sse x86_64-freebsd6 x86_64-netbsd \ diff -git a/contrib/reghunt/ChangeLog b/contrib/reghunt/ChangeLog diff -git a/contrib/config-list.mk b/contrib/config-list.mk Sebastian Huber * config-list.mk (LIST): Add arm-rtems. Joel Sherrill * config-list.mk (LIST): Add v850-rtems. diff -git a/contrib/ChangeLog b/contrib/ChangeLog dependencies = " = no then ISL_CHECK_VERSION(0,14) fi fi fi dnl Only execute fail-action, if ISL has been requested. Uros Bizjak PR target/47230 diff -git a/f b/f Release Manager * GCC 4.9.2 released. * f: Make more dependent on mpfr, mpc, isl, and cloog. -1,3 1,14 Tobias Burnus * configure.ac: Permit also ISL 0.14 with CLooG. Verified performance (small improvements on ARM).Ĭhange-Id: Ie79a45b21f92000dca07e34e849c0cf4cbc6761a Tested on projects that had issues with previous roll: TEST=cbuildbots: chromiumos-sdk, several boards for each platform. ![]() To experiment, users can start with the code below: program test The complete code to show the example plot is quite terse. In most cases, the calling routine should clean up the plot variable before moving on with the simple call: call destroy_plot(p) Complete Program CleanupĪfter the window is closed, the user’s program will continue execution. The appearance of the window will obviously differ depending on the platform (the example is from GNU/Linux). The call above will open a window and pause the user’s program execution until closed. Now that the plot is completely configured, we can actually display the plot: call display_plot(p) ![]() We could additionally set scaling on the axes, but the default behavior to autoscale the axes should be sufficient in many cases. Our axes should now appear properly labeled. In our case, we can use the following: call set_xlabel(p, "Easy") Labeling the AxesĪ proper plot should always have labeled axes. The pixel plot, like the scatter plot above, uses points for each datapoint, but the smaller pixel representation might be preferable when a substantial amount of data is being drawn. Another data set can be added and configured similarly, and it would be referenced using 1 as it’s index.ĭepending on the data, the user might prefer to use a line plot, bar chart, or the pixel plot. Note that the series is refered to as 0 since it is the first data set. To add a label and configure our data to appear in a scatter chart, we would call: call set_serieslabel(p, 0, "Example Data") Ĭall set_seriestype(p, 0, APLOT_STYLE_DOT) As mentioned in the reference section, the numbering for referencing series is zero-based. The data above should now be added to the plot as a series. Adding a Data SetĪplot can produce a handful of two-dimensional plots to visualize user data. At this point, the user may want to set up a plot title: call set_title(p, 'Example Plot')Īt this point, no data has been added. The call above creates a plot variable that is used in all subsequent calls to Aplot’s programming interface. ![]() The first step in creating a plot is to initialize a plot variable: type(aplot_t)::p Simply Fortran will take care of everything else necessary to include the Aplot library in an executable. Including the ModuleĪplot is accessible via a single Fortran 90 module: use aplot This tutorial is meant to provide the necessary steps for getting started with Aplot. Creating a graph from Fortran using Aplot is simple and easy. ![]()
0 Comments
Leave a Reply. |