Re: [PATCH 3/3] libdl: Add small data support to the remaining PowerPC BSPs.
Thanks, patch set looks good. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Question about PPPD Sample
Hello Alan, while porting the PPP support to libbsd I had some trouble to get it working. Maybe the example in libbsd helps: https://git.rtems.org/rtems-libbsd/tree/testsuite/ppp01/test_main.c I was able to connect and RTEMS system with my Linux host and connect via Telnet. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Project for GSoC 2019
Hello, After suggestions and response from Sebastian, Christian and Udit I started to explore the following ticket: #3338 : Port CHFS to RTEMS : https://devel.rtems.org/ticket/3338 Sebastian, even mentioned, that it can become a very good project for GSoC 2019. It would be great if any of the mentors want to mentor this project. I want to discuss this further and seek to work on this as my GSoC project for 2019. Also, please let me know if I am missing something. Thank you ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Coverity Scan Email to Build or Devel?
On Tue, Mar 5, 2019 at 8:16 PM Chris Johns wrote: > On 6/3/19 2:49 am, Joel Sherrill wrote: > > Hi > > > > I think it makes sense to have Coverity Scan send "analysis complete" > > emails to build@ or devel@. What do others think? > > I think build@. > I tried this yesterday and since it wasn't a whitelisted address, it didn't get through. > > > > > It will require whitelisting the automated email address they come from. > > > > What is the from address? > scan-ad...@coverity.com When you add it, ping me and I will do another run. --joel > > Chris > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Question about PPPD Sample
I am trying to establish a PPP connection between a Sparc/LEON3 RTEMS board and an ARM Linux board. I found a memory alignment error for the Sparc in the PPPD GetMask function, and I can submit a patch for that. After fixing the memory alignment problem, I am making more progress, but I have a fundamental question about the PPPD sample: In the sample’s PPPD app, when the PPPD_IPUP_HOOK is called, the hook sends RTEMS_SIGNAL_10 to the PPPD task, and the task calls rtems_ppp_disconnect. The PPP_IPDOWN_HOOK sends a signal that results in the task calling rtems_ppp_connect. Is the purpose of the PPPD sample to exercise the PPPD connect and disconnect code, and not to establish/maintain a connection? That is what I’m observing. It seems like as soon as the IP connection is up, the RTEMS side sends the disconnect request and they start all over again. Thanks, Alan ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: Update and Query regarding "mq_send: thread waiting: no preempt"
please push the changes offered by the patch On Sat, Mar 2, 2019 at 10:46 PM Shashvat Jain wrote: > Hello > Attached with this is a patch which adds some missing test names in the > /psxtmtests_plan.csv . > > the test case "mq_send: thread waiting: no preempt" should be made under a > different test name or within psxtmmq01 ? > > thank you > Regards > Shashvat > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
[PATCH] user/test: Update with the latest test configuration format.
From: Chris Johns --- user/testing/tests.rst | 110 +++-- 1 file changed, 96 insertions(+), 14 deletions(-) diff --git a/user/testing/tests.rst b/user/testing/tests.rst index 0b44d05..557cbc0 100644 --- a/user/testing/tests.rst +++ b/user/testing/tests.rst @@ -6,9 +6,9 @@ Test Banners All test output banners or strings are embedded in each test and the test -outputs them to the BSP's console as it executes. The RTEMS Tester captures the -BSP's console and uses this information to manage the state of the executing -test. The banner strings are: +outputs the banners to the BSP's console as it executes. The RTEMS Tester +captures the BSP's console and uses this information to manage the state of +the executing test. The banner strings are: .. _test-banner-begin: .. index:: test begin, TEST BEGIN @@ -65,10 +65,14 @@ test. The banner strings are: .. _test-states: .. index:: Test states -Test States +Test Controls +- + +The tests in the RTEMS kernel testsuite can be configured for each BSP. The +expected state of the test can be set as well as any configuration parameters +a test needs to run on a BSP. -The tests states are: +The test states are: .. index:: test state passed @@ -137,17 +141,46 @@ a tested is to ``pass``. If a test is known to fail it can have it's state set to ``expected-fail``. Setting tests that are known to fail to ``expected-fail`` lets everyone know a failure is not to be countered and consider a regression. -Expected test states are list in test configuration files that end with the -file extension ``.tcfg``. The testsuite supports global test configurations in -the ``testsuite/testdata`` directory. Global test states are applied to all -BSPs. BSPs can provide a test configuration that applies to just that BSP. +Expected test states are listed in test configuration files + +Test Configuration +^^ + +Tests can be configured for each BSP using test configuration files. These +files have the file extension ``.tcfg``. The testsuite supports global test +configurations in the ``testsuite/testdata`` directory. Global test states are +applied to all BSPs. BSPs can provide a test configuration that applies to +just that BSP and these files can include subsets of test configurations. + +The configuration supports: + +#. Including test configuration files to allow sharing of common + configurations. + +#. Excluding tests from being built that do not build for a BSP. + +#. Setting the test state if it is not ``passed``. -The test configuration file format is:: +#. Specifing a BSP specific build configuration for a test. - state: test test test +The test configuration file format is: -where ``test test test`` is a list of tests the state applies too. The ``state`` is one -of: +.. code-block:: none + + state: test + +where the ``state`` is state of the test and ``test`` is a comma separated +list of tests the state applies too. The configuration format is: + +.. code-block:: none + + flags: test: configuration + +where ``flags`` is the type of flags being set, the ``test`` is a comma +separate list of regular expresions that match the test the configuration +is applied too and the ``configuration`` is the string of flags. + +The ``state`` is one of: ``include`` The test list is the name of a test configuration file to include @@ -171,7 +204,56 @@ of: The tests listed are benchmarks. Benchmarks are flagged and not left to run to completion because they may take too long. +Specialized filtering using regular expressions is supported using: + +``rexclude`` + The test matching the regular expression are excluded. + +``rinclude`` + The tests matching the regular expression are included. + +By default all tests are included, specific excluded tests using the +``exclude`` state are excluded and cannot be included again. If a test +matching a ``rexclude`` regular it is excluded unless it is included using a +``rinclude`` regular expression. For example to build only the ``hello`` +sample application you can: + +.. code-block:: none + + rexclude .* + rinclude hello + +Test configuration flags can be applied to a range of tests using +flags. Currently only ``cflags`` is support. Tests need to support the +configuration for it to work. For example to configure a test: + +.. code-block:: none + + cflags: tm.*: -DTEST_CONFIG=42 + cflags: sp0[456]: -DA_SET_OF_TESTS=1 + +Flags setting are joined together and passed to the compiler's command +line. For example: + +.. code-block:: none + + cflags: tm.*: -DTEST_CONFIG=42 + cflags: tm03: -DTEST_TM03_CONFIG=1 + +would result in the command line to the test ``tm03`` being: + +.. code-block:: none + + -DTEST_CONFIG=42 -DTEST_TM03_CONFIG=1 + +Specific flags can be set for one test in a group. For example to set +a configuration for all timer tests and a special configuraiton for +one test: + +.. code-block:: none +
[PATCH 3/3] libdl: Add small data support to the remaining PowerPC BSPs.
From: Chris Johns
Updates #3687
---
.../gen5200/start/linkcmds.gen5200_base | 19 +-
bsps/powerpc/haleakala/start/linkcmds | 12
bsps/powerpc/mpc8260ads/start/linkcmds| 24 ---
bsps/powerpc/shared/start/linkcmds.share | 24 ++-
bsps/powerpc/ss555/start/linkcmds | 68 +++
bsps/powerpc/virtex4/start/linkcmds | 12 +++-
bsps/powerpc/virtex5/start/linkcmds | 12 +++-
cpukit/libdl/rtl-mdreloc-powerpc.c| 15
8 files changed, 144 insertions(+), 42 deletions(-)
diff --git a/bsps/powerpc/gen5200/start/linkcmds.gen5200_base
b/bsps/powerpc/gen5200/start/linkcmds.gen5200_base
index 5ab30882ce..ca9d50ebb5 100644
--- a/bsps/powerpc/gen5200/start/linkcmds.gen5200_base
+++ b/bsps/powerpc/gen5200/start/linkcmds.gen5200_base
@@ -27,6 +27,15 @@ RamBase = bsp_ram_start;
RamSize = bsp_ram_size;
HeapSize = DEFINED(HeapSize) ? HeapSize : 0x0;
+/*
+ * The upper layer linker command file may optionally define the symbol
+ * bsp_section_small_data_area_size. By default, the small data area is
+ * defined by the .sdata and .sbss input sections. Define
+ * bsp_section_small_data_area_size, if you want to make space available for
+ * dynamically loaded libraries (libdl). Small memory targets which do not use
+ * libdl, should not define this symbol.
+ */
+
MEMORY {
UNEXPECTED_SECTIONS : ORIGIN = 0x, LENGTH = 0
}
@@ -233,6 +242,7 @@ SECTIONS {
} > RAM
.sdata : {
+ bsp_section_sdata_begin = .;
PROVIDE (_SDA_BASE_ = 32768);
*(.sdata .sdata.* .gnu.linkonce.s.*)
@@ -245,13 +255,14 @@ SECTIONS {
* BSP: End of data section
*/
bsp_section_data_end = .;
+ bsp_section_sdata_end = .;
} > RAM
.sbss : {
/*
* BSP: Start of bss section
*/
- bsp_section_bss_start = .;
+ bsp_section_sbss_begin = .;
__bss_start = .;
@@ -260,11 +271,17 @@ SECTIONS {
*(.dynsbss)
*(.sbss .sbss.* .gnu.linkonce.sb.*)
PROVIDE (__sbss_end = .); PROVIDE (___sbss_end = .);
+ bsp_section_sbss_end = .;
+ bsp_section_sdata_libdl_begin = .;
+ . = DEFINED(bsp_section_small_data_area_size) ?
+ bsp_section_sdata_begin +
bsp_section_small_data_area_size : .;
+ bsp_section_sdata_libdl_end = .;
. = ALIGN (bsp_section_align);
} > RAM
.bss : {
+ bsp_section_bss_start = .;
*(COMMON)
*(.dynbss)
*(.bss .bss.* .gnu.linkonce.b.*)
diff --git a/bsps/powerpc/haleakala/start/linkcmds
b/bsps/powerpc/haleakala/start/linkcmds
index 7cd993c0c9..dad3e5cc76 100644
--- a/bsps/powerpc/haleakala/start/linkcmds
+++ b/bsps/powerpc/haleakala/start/linkcmds
@@ -24,6 +24,10 @@ MEMORY {
/*FLASH : ORIGIN = 0xFFE0, LENGTH = 16M*/
}
+/*
+ * Max sdata/bss.
+ */
+bsp_section_small_data_area_size = 65536;
SECTIONS
{
@@ -217,19 +221,27 @@ SECTIONS
.sdata : {
. = ALIGN (4);
PROVIDE (__SDATA_START__ = .);
+ bsp_section_sdata_begin = .;
sdata.start = .;
*(.sdata*)
*(.gnu.linkonce.s.*)
sdata.end = .;
+ bsp_section_sdata_end = .;
} > RAM
/* Zeroed small data addressed as offsets from r13 */
.sbss : {
. = ALIGN (4);
PROVIDE(__SBSS_START__ = .);
+ bsp_section_sbss_begin = .;
sbss.start = .;
*(.sbss .sbss.* *.gnu.linkonce.sb.*);
sbss.end = .;
+ bsp_section_sbss_end = .;
+ bsp_section_sdata_libdl_begin = .;
+ . = DEFINED(bsp_section_small_data_area_size) ?
+bsp_section_sdata_begin + bsp_section_small_data_area_size : .;
+ bsp_section_sdata_libdl_end = .;
} > RAM
PROVIDE(__SBSS_END__ = .);
diff --git a/bsps/powerpc/mpc8260ads/start/linkcmds
b/bsps/powerpc/mpc8260ads/start/linkcmds
index 84933b48e9..82550d41a8 100644
--- a/bsps/powerpc/mpc8260ads/start/linkcmds
+++ b/bsps/powerpc/mpc8260ads/start/linkcmds
@@ -100,7 +100,7 @@ SECTIONS
* end terminate with a NULL entry.
*/
-PROVIDE (__CTOR_LIST__ = .);
+PROVIDE (__CTOR_LIST__ = .);
/* LONG((__CTOR_END__ - __CTOR_LIST__) / 4 - 2) */
*crtbegin.o(.ctors)
*(.ctors)
@@ -227,28 +227,36 @@ SECTIONS
.fixup : { *(.fixup) } >ram
PROVIDE (_FIXUP_END_ = .);
PROVIDE (__FIXUP_END__ = .);
-
+
.sdata : {
+ bsp_section_sdata_begin = .;
PROVIDE (_SDA_BASE_ = 32768);
*(.sdata .sdata.* .gnu.linkonce.s.*)
-} > ram
-
+ bsp_section_sdata_end = .;
+ } > ram
+
.sbss : {
__bss_start = .;
-
+ bsp_section_sbss_begin = .;
+
PROVIDE (__sbss_start = .); PROVIDE (___sbss_start =
[PATCH 2/3] testsuite: Make the OPERATION_COUNT a test configuration parameter.
From: Chris Johns
- Add a small memory test config file.
- Update the small memory PowerPC BSPs to use the new test config.
---
.../hurricane/config/hurricane-testsuite.tcfg | 2 +-
.../rbtx4925/config/rbtx4925-testsuite.tcfg | 2 +-
.../rbtx4938/config/rbtx4938-testsuite.tcfg | 2 +-
.../moxiesim/config/moxiesim-testsuite.tcfg | 2 +-
.../mpc55xxevb/config/gwlcfm-testsuite.tcfg | 2 +-
.../config/mpc5566evb-testsuite.tcfg | 6 +-
.../config/mpc5566evb_spe-testsuite.tcfg | 6 +-
.../config/mpc5643l_dpu-testsuite.tcfg| 62 +--
.../config/mpc5643l_evb-testsuite.tcfg| 62 +--
.../mpc55xxevb/config/mpc5668g-testsuite.tcfg | 4 +-
.../config/mpc5674f_ecu508_app-testsuite.tcfg | 5 +-
.../mpc5674f_ecu508_boot-testsuite.tcfg | 8 +-
.../config/mpc5674f_rsm6-testsuite.tcfg | 8 +-
.../config/mpc5674fevb-testsuite.tcfg | 4 +-
.../config/mpc5674fevb_spe-testsuite.tcfg | 4 +-
.../config/phycore_mpc5554-testsuite.tcfg | 5 +-
.../qoriq/config/qoriq_core_0-testsuite.tcfg | 2 +-
.../qoriq/config/qoriq_core_1-testsuite.tcfg | 2 +-
.../qoriq/config/qoriq_e500-testsuite.tcfg| 2 +-
.../config/qoriq_e6500_32-testsuite.tcfg | 2 +-
.../config/qoriq_e6500_64-testsuite.tcfg | 2 +-
testsuites/aclocal/rtems-test-check.m4| 8 +-
testsuites/psxtests/psxaio03/init.c | 25 +--
testsuites/psxtests/psxaio03/system.h | 16 +-
testsuites/psxtmtests/Makefile.am | 165 ++
testsuites/psxtmtests/psxtmbarrier01/init.c | 4 +
testsuites/psxtmtests/psxtmbarrier02/init.c | 8 +-
testsuites/psxtmtests/psxtmbarrier03/init.c | 4 +
testsuites/psxtmtests/psxtmbarrier04/init.c | 5 +
.../psxtmtests/psxtmbarrierattr01/init.c | 4 +
testsuites/psxtmtests/psxtmcleanup01/init.c | 4 +
testsuites/psxtmtests/psxtmcond08/init.c | 4 +
testsuites/psxtmtests/psxtmmutex02/init.c | 6 +-
testsuites/psxtmtests/psxtmmutex06/init.c | 6 +-
testsuites/psxtmtests/psxtmsem03/init.c | 6 +-
testsuites/psxtmtests/psxtmthread01/init.c| 6 +-
testsuites/sptests/sp71/init.c| 6 +-
...this-bsp.tcfg => disable-libdl-tests.tcfg} | 7 +-
.../testdata/small-memory-testsuite.tcfg | 19 ++
testsuites/tmtests/Makefile.am| 83 -
testsuites/tmtests/configure.ac | 3 -
testsuites/tmtests/tm01/task1.c | 4 +
testsuites/tmtests/tm02/task1.c | 4 +
testsuites/tmtests/tm03/task1.c | 4 +
testsuites/tmtests/tm04/task1.c | 4 +
testsuites/tmtests/tm06/task1.c | 4 +
testsuites/tmtests/tm07/task1.c | 4 +
testsuites/tmtests/tm08/task1.c | 4 +
testsuites/tmtests/tm09/task1.c | 4 +
testsuites/tmtests/tm10/task1.c | 4 +
testsuites/tmtests/tm11/task1.c | 4 +
testsuites/tmtests/tm12/task1.c | 4 +
testsuites/tmtests/tm13/task1.c | 4 +
testsuites/tmtests/tm14/task1.c | 4 +
testsuites/tmtests/tm15/task1.c | 4 +
testsuites/tmtests/tm16/task1.c | 4 +
testsuites/tmtests/tm17/task1.c | 4 +
testsuites/tmtests/tm18/task1.c | 4 +
testsuites/tmtests/tm20/task1.c | 4 +
testsuites/tmtests/tm21/task1.c | 4 +
testsuites/tmtests/tm22/task1.c | 4 +
testsuites/tmtests/tm23/task1.c | 4 +
testsuites/tmtests/tm24/task1.c | 4 +
testsuites/tmtests/tm25/task1.c | 4 +
testsuites/tmtests/tm26/task1.c | 4 +
testsuites/tmtests/tm28/task1.c | 4 +
testsuites/tmtests/tm29/task1.c | 4 +
testsuites/tmtests/tm30/init.c| 10 +-
testsuites/tmtests/tmck/task1.c | 8 +-
testsuites/tmtests/tmoverhd/testtask.c| 4 +
70 files changed, 335 insertions(+), 374 deletions(-)
rename testsuites/testdata/{dltests-broken-on-this-bsp.tcfg =>
disable-libdl-tests.tcfg} (75%)
create mode 100644 testsuites/testdata/small-memory-testsuite.tcfg
diff --git a/bsps/mips/hurricane/config/hurricane-testsuite.tcfg
b/bsps/mips/hurricane/config/hurricane-testsuite.tcfg
index fb84b55762..8d039b6993 100644
--- a/bsps/mips/hurricane/config/hurricane-testsuite.tcfg
+++ b/bsps/mips/hurricane/config/hurricane-testsuite.tcfg
@@ -2,4 +2,4 @@
# This is the set of tests which are known to not link on this BSP
#
-include: testdata/dltests-broken-on-this-bsp.tcfg
+include: testdata/disable-libdl-tests.tcfg
diff --git a/bsps/mips/rbtx4925/config/rbtx4925-testsuite.tcfg
b/bsps/mips/rbtx4925/config/rbtx4925-testsuite.tcfg
index fb84b55762..8d039b6993 100644
--- a/bsps/mips/rbtx4925/config/rbtx4925-testsuite.tcfg
+++ b/bsps/mips/rbtx4925/config/rbtx4925-testsuite.tcfg
@@ -2,4
[PATCH 1/3] testsuite: Add rexclude, rinclude and cflags to test config files.
From: Chris Johns
---
testsuites/rtems-test-check.py | 94 ++
1 file changed, 83 insertions(+), 11 deletions(-)
diff --git a/testsuites/rtems-test-check.py b/testsuites/rtems-test-check.py
index 8eef1a01c1..8af841957f 100755
--- a/testsuites/rtems-test-check.py
+++ b/testsuites/rtems-test-check.py
@@ -37,6 +37,8 @@ from __future__ import print_function
import os
import os.path
+import re
+import sre_constants
import sys
def eprint(*args, **kwargs):
@@ -82,7 +84,7 @@ if verbose:
#
if mode == 'exclude':
pass
-elif mode == 'flags':
+elif mode == 'cflags':
if len(tests) != 1:
eprint('error: test count not 1 for mode: %s' % (mode))
print('INVALID-TEST-DATA')
@@ -103,13 +105,19 @@ states = ['exclude',
'expected-fail',
'user-input',
'indeterminate',
- 'benchmark']
+ 'benchmark',
+ 'rexclude',
+ 'rinclude']
+flags = ['cflags']
defines = { 'expected-fail' : '-DTEST_STATE_EXPECTED_FAIL=1',
'user-input': '-DTEST_STATE_USER_INPUT=1',
'indeterminate' : '-DTEST_STATE_INDETERMINATE=1',
'benchmark' : '-DTEST_STATE_BENCHMARK=1' }
output = []
-testdata = {}
+testdata = { 'flags': {} }
+
+for f in flags:
+testdata['flags'][f] = {}
if verbose:
eprint('mode: %s' % (mode))
@@ -145,9 +153,9 @@ while len(testconfig):
lc = 0
for line in tdata:
lc += 1
-ls = [s.strip() for s in line.split(':')]
if len(line) == 0:
continue
+ls = [s.strip() for s in line.split(':', 1)]
if verbose:
eprint('%4d: %s' % (lc, line))
if len(ls) != 2:
@@ -161,27 +169,91 @@ while len(testconfig):
if td is None:
eprint('error: include not found: %s:%d' % (tc, lc))
print('INVALID-TEST-DATA')
+sys.exit(1)
testconfig.insert(0, td)
if verbose:
eprint('include: %s' % (', '.join(testconfig)))
+elif state in flags:
+fs = test.split(':', 1)
+if len(fs) != 2:
+eprint('error: syntax error: %s:%d' % (tc, lc))
+print('INVALID-TEST-DATA')
+sys.exit(1)
+ftests = [t.strip() for t in fs[0].split(',')]
+if verbose:
+eprint('%4d: %r : %s' % (lc, ftests, fs[1]))
+for test in ftests:
+if test not in testdata['flags'][state]:
+testdata['flags'][state][test] = [fs[1]]
+else:
+testdata['flags'][state][test] += [fs[1]]
elif state in states:
+stests = [t.strip() for t in test.split(',')]
if state not in testdata:
-testdata[state] = [test]
+testdata[state] = stests
else:
-testdata[state] += [test]
+testdata[state] += stests
else:
eprint('error: invalid test state: %s in %s:%d' % (state, tc, lc))
print('INVALID-TEST-DATA')
sys.exit(1)
+if mode in flags:
+for state in ['exclude', 'rexclude', 'rinclude']:
+states.remove(state)
+
for test in tests:
if mode == 'exclude':
-if 'exclude' not in testdata or test not in testdata['exclude']:
+#
+# Exclude is the highest priority, do this first
+#
+if 'exclude' in testdata and test in testdata['exclude']:
+exclude = True
+else:
+#
+# Regx exclude then regx include so you can filter a whole
+# group and add back some.
+#
+exclude = False
+if 'rexclude' in testdata:
+for e in testdata['rexclude']:
+try:
+m = re.compile(e).match(test)
+except sre_constants.error as ree:
+eprint('error: invalid rexclude regx: %s: %s' % (e,
ree))
+print('INVALID-TEST-DATA')
+sys.exit(1)
+if m:
+exclude = True
+if 'rinclude' in testdata:
+for i in testdata['rinclude']:
+try:
+m = re.compile(i).match(test)
+except sre_constants.error as ree:
+eprint('error: invalid rinclude regx: %s:
%s' % (i, ree))
+print('INVALID-TEST-DATA')
+sys.exit(1)
+if m:
+exclude = False
+#
+# If not excluded add the test to the output
+#
+if not exclude:
output += [test]
-elif mode == 'flags':
-for state in states:
-
Re: Query Regarding Old Projects, for GSoC 2019
I'm not sure if the project is open, but if it is, I'd be willing to co-mentor. On Wed, Mar 6, 2019, 2:45 PM Vaibhav Gupta wrote: > I was exploring for more open projects and found the following one. > > - Port V8 Javascript Engine : > https://devel.rtems.org/wiki/Developer/Projects/Open/V8 > > Not much information is given about it and even the above link was > modified in 2015. I want to know if the project is open for GSOC 2019? > If it is open, then It would be great to know if someone would like to > mentor it. I would like to discuss further on it. > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Query Regarding Old Projects, for GSoC 2019
I was exploring for more open projects and found the following one. - Port V8 Javascript Engine : https://devel.rtems.org/wiki/Developer/Projects/Open/V8 Not much information is given about it and even the above link was modified in 2015. I want to know if the project is open for GSOC 2019? If it is open, then It would be great to know if someone would like to mentor it. I would like to discuss further on it. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
